diff options
Diffstat (limited to 'drivers/staging/lustre/lustre/include/cl_object.h')
| -rw-r--r-- | drivers/staging/lustre/lustre/include/cl_object.h | 14 |
1 files changed, 9 insertions, 5 deletions
diff --git a/drivers/staging/lustre/lustre/include/cl_object.h b/drivers/staging/lustre/lustre/include/cl_object.h index 4d692dcd96cf..c809239c0866 100644 --- a/drivers/staging/lustre/lustre/include/cl_object.h +++ b/drivers/staging/lustre/lustre/include/cl_object.h @@ -1314,7 +1314,7 @@ static inline int __page_in_use(const struct cl_page *page, int refc) * calls. To achieve this, every layer can implement ->clo_fits_into() method, * that is called by lock matching code (cl_lock_lookup()), and that can be * used to selectively disable matching of certain locks for certain IOs. For - * exmaple, lov layer implements lov_lock_fits_into() that allow multi-stripe + * example, lov layer implements lov_lock_fits_into() that allow multi-stripe * locks to be matched only for truncates and O_APPEND writes. * * Interaction with DLM @@ -2385,14 +2385,18 @@ struct cl_io { * Check if layout changed after the IO finishes. Mainly for HSM * requirement. If IO occurs to openning files, it doesn't need to * verify layout because HSM won't release openning files. - * Right now, only two opertaions need to verify layout: glimpse + * Right now, only two operations need to verify layout: glimpse * and setattr. */ ci_verify_layout:1, /** * file is released, restore has to to be triggered by vvp layer */ - ci_restore_needed:1; + ci_restore_needed:1, + /** + * O_NOATIME + */ + ci_noatime:1; /** * Number of pages owned by this IO. For invariant checking. */ @@ -2552,7 +2556,7 @@ struct cl_req_obj { */ struct cl_req { enum cl_req_type crq_type; - /** A list of pages being transfered */ + /** A list of pages being transferred */ struct list_head crq_pages; /** Number of pages in cl_req::crq_pages */ unsigned crq_nrpages; @@ -3224,7 +3228,7 @@ void cl_sync_io_note(struct cl_sync_io *anchor, int ioret); * * - call chains have no non-lustre portions inserted between lustre code. * - * On a client both these assumtpion fails, because every user thread can + * On a client both these assumption fails, because every user thread can * potentially execute lustre code as part of a system call, and lustre calls * into VFS or MM that call back into lustre. * |