staging/lustre: Remove liblustre references from explanations

Since liblustre is no longer with us, referencing to it in the
explanations only makes things less clear

Signed-off-by: Oleg Drokin <green@linuxhacker.ru>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
Oleg Drokin 2016-02-26 01:49:56 -05:00 committed by Greg Kroah-Hartman
parent 71842aecef
commit 85f552dfa6
5 changed files with 5 additions and 7 deletions

View File

@ -697,7 +697,7 @@ enum cl_page_type {
/** Transient page, the transient cl_page is used to bind a cl_page /** Transient page, the transient cl_page is used to bind a cl_page
* to vmpage which is not belonging to the same object of cl_page. * to vmpage which is not belonging to the same object of cl_page.
* it is used in DirectIO, lockless IO and liblustre. * it is used in DirectIO and lockless IO.
*/ */
CPT_TRANSIENT, CPT_TRANSIENT,
}; };
@ -2282,7 +2282,7 @@ enum cl_io_lock_dmd {
CILR_MANDATORY = 0, CILR_MANDATORY = 0,
/** Layers are free to decide between local and global locking. */ /** Layers are free to decide between local and global locking. */
CILR_MAYBE, CILR_MAYBE,
/** Never lock: there is no cache (e.g., liblustre). */ /** Never lock: there is no cache (e.g., lockless IO). */
CILR_NEVER CILR_NEVER
}; };

View File

@ -54,7 +54,7 @@
#define LL_MAX_BLKSIZE (1UL<<LL_MAX_BLKSIZE_BITS) #define LL_MAX_BLKSIZE (1UL<<LL_MAX_BLKSIZE_BITS)
/* /*
* This is embedded into liblustre and llite super-blocks to keep track of * This is embedded into llite super-blocks to keep track of
* connect flags (capabilities) supported by all imports given mount is * connect flags (capabilities) supported by all imports given mount is
* connected to. * connected to.
*/ */

View File

@ -658,7 +658,7 @@ enum obd_notify_event {
/* /*
* Data structure used to pass obd_notify()-event to non-obd listeners (llite * Data structure used to pass obd_notify()-event to non-obd listeners (llite
* and liblustre being main examples). * being main example).
*/ */
struct obd_notify_upcall { struct obd_notify_upcall {
int (*onu_upcall)(struct obd_device *host, struct obd_device *watched, int (*onu_upcall)(struct obd_device *host, struct obd_device *watched,

View File

@ -483,7 +483,6 @@ EXPORT_SYMBOL(cl_site_stats_print);
* because Lustre code may call into other fs which has certain assumptions * because Lustre code may call into other fs which has certain assumptions
* about journal_info. Currently following fields in task_struct are identified * about journal_info. Currently following fields in task_struct are identified
* can be used for this purpose: * can be used for this purpose:
* - cl_env: for liblustre.
* - tux_info: only on RedHat kernel. * - tux_info: only on RedHat kernel.
* - ... * - ...
* \note As long as we use task_struct to store cl_env, we assume that once * \note As long as we use task_struct to store cl_env, we assume that once

View File

@ -223,8 +223,7 @@ static int osc_lock_unuse(const struct lu_env *env,
/* /*
* Move lock into OLS_RELEASED state before calling * Move lock into OLS_RELEASED state before calling
* osc_cancel_base() so that possible synchronous cancellation * osc_cancel_base() so that possible synchronous cancellation
* (that always happens e.g., for liblustre) sees that lock is * sees that lock is released.
* released.
*/ */
ols->ols_state = OLS_RELEASED; ols->ols_state = OLS_RELEASED;
return osc_lock_unhold(ols); return osc_lock_unhold(ols);