diff options
| author |   Patrick Farrell <paf@cray.com> | 2016-08-16 16:19:12 -0400 |
|---|---|---|
| committer |   Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2016-08-21 15:57:38 +0200 |
| commit | aa08b0e3c7ae977ed9384f63ded2743e0aee1c7e (patch) | |
| tree | 3cf757e7bf1011136ae789818e95401f5309f354 | |
| parent | staging: lustre: mdc: always use D_INFO for debug info when mdc_put_rpc_lock fails (diff) | |
| download | linux-dev-aa08b0e3c7ae977ed9384f63ded2743e0aee1c7e.tar.xz linux-dev-aa08b0e3c7ae977ed9384f63ded2743e0aee1c7e.zip | |
staging: lustre: fld: add fld description documentation
Add subsystem description from Di Wang to header file.
Signed-off-by: Patrick Farrell <paf@cray.com>
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-5153
Reviewed-on: http://review.whamcloud.com/10631
Reviewed-by: wangdi <di.wang@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
Signed-off-by: James Simmons <jsimmons@infradead.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| -rw-r--r-- | drivers/staging/lustre/lustre/fld/fld_internal.h | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/drivers/staging/lustre/lustre/fld/fld_internal.h b/drivers/staging/lustre/lustre/fld/fld_internal.h index f0efe5b9fbec..08eaec735d6f 100644 --- a/drivers/staging/lustre/lustre/fld/fld_internal.h +++ b/drivers/staging/lustre/lustre/fld/fld_internal.h @@ -31,6 +31,25 @@ * * lustre/fld/fld_internal.h * + * Subsystem Description: + * FLD is FID Location Database, which stores where (IE, on which MDT) + * FIDs are located. + * The database is basically a record file, each record consists of a FID + * sequence range, MDT/OST index, and flags. The FLD for the whole FS + * is only stored on the sequence controller(MDT0) right now, but each target + * also has its local FLD, which only stores the local sequence. + * + * The FLD subsystem usually has two tasks: + * 1. maintain the database, i.e. when the sequence controller allocates + * new sequence ranges to some nodes, it will call the FLD API to insert the + * location information <sequence_range, node_index> in FLDB. + * + * 2. Handle requests from other nodes, i.e. if client needs to know where + * the FID is located, if it can not find the information in the local cache, + * it will send a FLD lookup RPC to the FLD service, and the FLD service will + * look up the FLDB entry and return the location information to client. + * + * * Author: Yury Umanets <umka@clusterfs.com> * Author: Tom WangDi <wangdi@clusterfs.com> */ |