Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nydus-image: fix some comments #476

Merged
merged 1 commit into from
Jun 9, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/bin/nydus-image/core/node.rs
Original file line number Diff line number Diff line change
Expand Up @@ -193,7 +193,7 @@ pub struct Node {
/// Device id associated with the source inode.
///
/// A source directory may contain multiple partitions from different hard disk, so
/// a pair of (dev, read_ino) is needed to uniquely identify an inode from source directory.
/// a pair of (real_ino, dev) is needed to uniquely identify an inode from source directory.
pub src_dev: u64,
/// Inode number of the source inode.
pub src_ino: Inode,
Expand Down
2 changes: 1 addition & 1 deletion src/bin/nydus-image/core/prefetch.rs
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ use crate::node::Node;
pub enum PrefetchPolicy {
None,
/// Readahead will be issued from Fs layer, which leverages inode/chunkinfo to prefetch data
/// from blob no mather where it resides(OSS/Localfs). Basically, it is willing to cache the
/// from blob no matter where it resides(OSS/Localfs). Basically, it is willing to cache the
/// data into blobcache(if exists). It's more nimble. With this policy applied, image builder
/// currently puts readahead files' data into a continuous region within blob which behaves very
/// similar to `Blob` policy.
Expand Down