LU-17609 sec: nodemap readonly_mount for remount The readonly_mount property on nodemaps forces read-only mount from clients. Clients trying rw remount (via mount -o remount,rw) should also be forced to read-only. Also improve sanity-sec test_61 to exercise client remount. Fixes: e7ce67de92 ("LU-15451 sec: read-only nodemap flag") Signed-off-by: Sebastien Buisson <sbuisson@ddn.com> Change-Id: I61f8141001d2ff9e832e5c93d8f5997479af98a6 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/54282 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Arshad Hussain <arshad.hussain@aeoncomputing.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-14535 quota: get all quota info in LFS This patch adds option "-a" for LFS to get the quota info of all quota IDs. it iterates quota setting saved in global quota setting files "quota_master/md-0x0" and "quota_master/dt-0x0" from QMT and iterates the quota usage info saved in acct quota files in the backend FS (LDiskFS or ZFS) from QSDs, then merge the two kinds of quota info at client and print it in the similar way as "lfs quota -u|-g|-p". $lfs quota -a -u /mnt/lustre Filesystem /mnt/lustre, Disk usr quotas quota_id kbytes quota limit grace files quota limit grace root 9684 0 0 - 1019 0 0 - bin 4 0 102400 - 1 0 10240 - daemon 4 0 102400 - 1 0 10240 - adm 4 0 102400 - 1 0 10240 - lp 4 0 102400 - 1 0 10240 - sync 4 0 102400 - 1 0 10240 - shutdown 4 0 102400 - 1 0 10240 - halt 4 0 102400 - 1 0 10240 - mail 4 0 102400 - 1 0 10240 - $lfs quota -a -g /mnt/lustre Filesystem /mnt/lustre, Disk grp quotas quota_id kbytes quota limit grace files quota limit grace root 9684 0 0 - 1019 0 0 - bin 4 0 204800 - 1 0 20480 - daemon 4 0 204800 - 1 0 20480 - adm 4 0 204800 - 1 0 20480 - lp 4 0 204800 - 1 0 20480 - sync 4 0 204800 - 1 0 20480 - shutdown 4 0 204800 - 1 0 20480 - halt 4 0 204800 - 1 0 20480 - mail 4 0 204800 - 1 0 20480 - This patch also fixes an deadlock issue in qmt_pool_recalc, the rw_semaphore "qmt_pool_info.qpi_sarr.osts.op_rw_sem" has been acquired in qmt_pool_recalc (read mode), but it was acquired once more in qmt_seed_glbe_all (read mode) and will be stuck if there is a pending write mode lock acquisition from another thread. qsd_reint_qpool D Call Trace: schedule+0x29/0x70 rwsem_down_read_failed+0x105/0x1c0 call_rwsem_down_read_failed+0x18/0x30 down_read+0x20/0x40 qmt_seed_glbe_all+0x3a0/0x800 [lquota] qmt_site_recalc_cb+0x3c7/0x800 [lquota] cfs_hash_for_each_tight+0x11e/0x330 cfs_hash_for_each+0x10/0x20 [libcfs] qmt_pool_recalc+0x9fc/0x1310 [lquota] llog_process_th D Call Trace: schedule+0x29/0x70 rwsem_down_write_failed+0x215/0x3c0 call_rwsem_down_write_failed+0x17/0x30 down_write+0x2d/0x3d lu_tgt_pool_remove+0x36/0x1e0 [obdclass] qmt_pool_add_rem+0x655/0x920 [lquota] qmt_pool_rem+0x10/0x20 [lquota] lod_pool_remove_q+0xd6/0x1d0 [lod] class_process_config+0x16f2/0x2b20 class_config_llog_handler+0x839/0x1540 llog_process_thread+0x913/0x1c10 llog_process_thread_daemonize+0x9f/0xe0 Test-Parameters: testlist=sanity-quota env=SLOW=yes,ONLY=49,NUM_QIDS=20000 Change-Id: I08feb928fbf34635ec9c5c341de993c718798dc9 Signed-off-by: Hongchao Zhang <hongchao@whamcloud.com> Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/42098 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: James Simmons <jsimmons@infradead.org> Reviewed-by: Sergey Cheremencev <scherementsev@ddn.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
LU-13048 mdd: allow release after a non-blocking migrate lfs setstripe -i0 file lfs hsm_archive file lfs migrate -n -i1 file lfs hsm_release file These actions lead to "Cannot send HSM request ...: Operation not permitted". This happens because of data version mismatch. This error is returned by mdt_hsm_release() when the data versions are not the same. This patch only corrects the non-blocking migrations. mdd_swap_layouts is updated to check and update the HSM archive version when possible. The new and old data versions are added as arguments to this function. If the old data version does not match the data version in the HSM attribute, we don't update the HSM attribute because we don't know what caused the inconsistency. During a swap between a volatile and a regular file, if both objects have an HSM xattr, mdd_swap_layouts was called from the MDT HSM layer (release and restore). In this case, we want to swap the HSM xattr (previously done using SWAP_LAYOUTS_MDS_HSM as a last argument to mdd_swap_layouts). If only the regular file has an HSM attribute, mdd_swap_layouts was called after a migration (blocking or not). In this case, we want to update the HSM archive version only if the file is not dirty and if the new data version is provided. Also, this patch removes the CL_LAYOUT event that was emitted for a release. Since a CL_HSM event with HE_RELEASE flag is also emitted, the CL_LAYOUT is unecessary. For "lfs swap_layouts", the operation is denied on 2 files with HSM xattr (HSM xattr swap will cause inconsistencies). With non-HSM file and archived file, the operation is allowed but the dirty flag is set on the HSM file. Add lustre_swab_close_data_special() to swab close_data fields inside the union (specific to some types of close). Add regression test sanity-hsm 607a, 607b and 607c. Test-Parameters: clientversion=2.15.4 testlist=sanity-hsm Test-Parameters: serverversion=2.15.4 testlist=sanity-hsm env=EXCEPT="114 409a" Test-Parameters: testlist=sanity-hsm env=ONLY=607,ONLY_REPEAT=15 Signed-off-by: Courrier Guillaume <guillaume.courrier@cea.fr> Signed-off-by: Etienne AUJAMES <eaujames@ddn.com> Change-Id: I6e90131235f96255b636eea366ad0cef5f4f0b19 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/49236 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: James Simmons <jsimmons@infradead.org> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-17200 mdt: check object's locality remote object can disappear while we're getting an ldlm lock for it. we can't check object's attributes before we're sure it does exist. so check object's locality first. Signed-off-by: Alex Zhuravlev <bzzz@whamcloud.com> Change-Id: I86ad0f3e7c38b0dce51a9fd836ba2293b210fe4f Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/52716 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Mikhail Pershin <mpershin@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
LU-12273 lod: metadata overstriping This adds overstriping for MDTs, similar to overstriping for OSTs (added in LU-9846). This adds a new option to setdirstripe, -C, allowing creation of more than one stripe per MDT. It is also possible to place multiple stripes on the same MDT using specific striping with -m. This allows a single directory to more fully use the full capability of each MDT in the file system. Two limitations of note: 1. This requires > 1 MDT, otherwise the DNE subsystem is not initialized. 2. Due to recovery limitations, we allow a max of only 5 stripes per MDT. MDT overstriping increases mdtest-hard-write performance by up to 13%, mdtest-hard-stat by 93%, at the cost of a slight drop in mdtest-hard-read (7%), with no change in delete. 4 MDTs, 1 stripe/MDT: mdtest-hard-write 117.399467 kIOPS : time 339.496 seconds mdtest-hard-stat 727.020749 kIOPS : time 55.666 seconds mdtest-hard-read 245.556392 kIOPS : time 162.897 seconds mdtest-hard-delete 104.379111 kIOPS : time 382.710 seconds 4 MDTs, 4 stripes/MDTs: mdtest-hard-write 132.963290 kIOPS : time 309.093 seconds mdtest-hard-stat 1408.161148 kIOPS : time 30.107 seconds mdtest-hard-read 229.383910 kIOPS : time 179.576 seconds mdtest-hard-delete 103.284369 kIOPS : time 398.442 seconds Test-Parameters: testlist=sanity env=ONLY=300u serverversion=2.14.0 Signed-off-by: Patrick Farrell <pfarrell@whamcloud.com> Signed-off-by: Qian Yingjin <qian@ddn.com> Signed-off-by: Lai Siyao <lai.siyao@whamcloud.com> Change-Id: I11556b223029820bd335e87c7bf073970e03468d Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/35034 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-6142 mdt: Fix style issues for mdt_handler.c This patch fixes issues reported by checkpatch for file lustre/mdt/mdt_handler.c Test-Parameters: trivial Signed-off-by: Arshad Hussain <arshad.hussain@aeoncomputing.com> Change-Id: Iab06a6074c7448ba631cc8b83151253cc8b35fa2 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/54062 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Timothy Day <timday@amazon.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-17297 grant: move tgt_grant_sanity_check() calls Call tgt_grant_sanity_check() in ofd_obd_disconnect() and in mdt_obd_disconnect() after call to tgt_grant_discard(). Otherwise, sum of grants does not match to total grant counter which is reported as LustreError: ofd_obd_disconnect: tot_granted 0 != fo_tot_granted 8388608 This is because on stale export eviction class_disconnect_stale_exports() moves stale exports to separate list but does not update obd's grant counters. Test to illustrate the issue is included. HPE-bug-id: LUS-11469 Signed-off-by: Vladimir Saveliev <vladimir.saveliev@hpe.com> Change-Id: I0b4568b88a2fe7b50f4eac50b4b064d7afbc7a75 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/53171 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Patrick Farrell <pfarrell@whamcloud.com> Reviewed-by: Mikhail Pershin <mpershin@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
LU-17426 mdt: relax same MDT file rename lock Allow cross-directory rename of regular files (strictly, any non-directory) on the same MDT without holding the BigFilesystemLock (BFL), as file renames cannot change the directory hierarchy. This should improve the performance for these rename operations, and reduce contention between local MDT file renames in different parts of the directory tree. Add "mdt.*.enable_parallel_rename_crossdir" parameter to disable cross-directory file renames if there is an issue with this change. Signed-off-by: Lai Siyao <lai.siyao@whamcloud.com> Change-Id: I511b392e46c46140cac6aa3ede02bfe793729f7f Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/53726 Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Hongchao Zhang <hongchao@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com>
LU-13307 nodemap: have nodemap_add_member support large NIDs Currently when mounting lustre using IPv6 address fails with Lustre: 27361:0:(nodemap_handler.c:395:nodemap_add_member()) lustre-MDT0000: error adding to nodemap, no valid NIDs found LustreError: 11-0: lustre-MDT0000-osp-MDT0003: operation mds_connect to node 0@lo failed: rc = -22 This was due to no nodemap being set so the ptlrpc layer was not seeing any new peers. Adding minimal support to nodemap allows mounting. Change-Id: If9cfe88ec92afc3f14788f3f3ded8387a1b5d8c7 Signed-off-by: James Simmons <jsimmons@infradead.org> Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/53135 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Sebastien Buisson <sbuisson@ddn.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-17144 mdt: set dmv by setxattr Client side: convert setxattr("trusted.dmv") to "setdirstripe -D", as will help restore directory default LMV from backup. Server side: add a tunable to enable setxattr("trusted.dmv"), it can be turned on by "lctl set_param -n mdt.*.enable_dmv_xattr=1". It's off by default. Since empty buffer can be set by setxattr, add check in server code to avoid crash. Add sanity 413j. Test-Parameter: serverversion=2.14 mdtcount=4 testlist=sanity env=ONLY=413j Signed-off-by: Lai Siyao <lai.siyao@whamcloud.com> Change-Id: I27d784998a9c4a182b4fffb8b06c84e9d9190919 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/52510 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Hongchao Zhang <hongchao@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
LU-16837 lustre: avoid the same member name There are several structures using the same member name, such as cl_ladvise_io::li_flags, layout_intent::li_flags and lfsck_instance::li_flags, and this makes it hard to find where it is used. This patch renames some structures member prefix to avoid the homonyms. Test-Parameters: trivial Signed-off-by: Bobi Jam <bobijam@whamcloud.com> Change-Id: Ie592afa06dd0abf0c1110843e5d8007a91c68145 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/51766 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Arshad Hussain <arshad.hussain@aeoncomputing.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-17307 mdt: get dirent count by request Add MA_DIRENT_CNT/LA_DIRENT_CNT to notify osd to get dirent count. Set it in mdt_getattr_name_lock() and when auto-split is enabled so it won't cause overhead when auto-split is disabled, and change oo_dirent_count type to atomic_t so the result does not become inaccurate over time from repeated addition/removal (which may be used to know whether directory is empty or compare directories in the future). In osd_dirent_count() set oo_dirent_count to 0 before iteration to avoid multiple threads iterate at the same time, which means the result may not be accurate in this case, but it will be eventually. Fixes: 03a4431dac ("LU-11025 osd: osd_attr_get() returns dirent count") Signed-off-by: Lai Siyao <lai.siyao@whamcloud.com> Change-Id: I2be6c0dcfda1c98995a269585c5d8d781a8a3b42 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/53229 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Hongchao Zhang <hongchao@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
LU-9859 libcfs: refactor libcfs initialization. Many lustre modules depend on libcfs having initialized properly, but do not explicit check that it did. When lustre is built as discrete modules, this does not cause a problem because if the libcfs module fails initialization, the other modules don't even get loaded. When lustre is compiled into the kernel, all module_init() routines get run, so they need to check the required initialization succeeded. This patch splits out the initialization of libcfs into a new libcfs_setup(), and has all modules call that. The misc_register() call is kept separate as it does not allocate any resources and if it fails, it fails hard - no point in retrying. Other set-up allocates resources and so is best delayed until they are needed, and can be worth retrying. Ideally, the initialization would happen at mount time (or similar) rather than at load time. Doing this requires each module to check dependencies when they are activated rather than when they are loaded. Achieving that is a much larger job that would have to progress in stages. For now, this change ensures that if some initialization in libcfs fails, other modules will fail-safe. Linux-commit: 64bf0b1a079d61e9e059b9dc7a58e064c7d994ae Change-Id: I6b5ecdba0defc6e033f78d8fc2b9be9e26c7f720 Signed-off-by: Mr. NeilBrown <neilb@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/52700 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Timothy Day <timday@amazon.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-17015 gss: avoid request replay Lustre's upcall cache has a retry mechanism in case the upcall was interrupted or failed and we timed out waiting. In this case we do our best to retry and do the upcall again. But when the upcall cache is used for GSS contexts, the upcall cannot be done twice with same data. The GSSAPI implements security measures that forbids that kind of request replay, to prevent man-in-the-middle attacks for instance. Add a new uc_acquire_replay field to struct upcall_cache, so that upcall cache users can tell if acquire upcall can be replayed. For identity upcall, this replay is fine. But for GSS contexts we need to avoid those replays. And bump upcall cache timeout value from 20s to 30s for GSS context init requests. Also add more debug messages to gss code for both client and server sides, and both kernel and userspace. Test-Parameters: kerberos=true testlist=sanity-krb5 Signed-off-by: Sebastien Buisson <sbuisson@ddn.com> Change-Id: I56decc83a4f0d21be420e87cb0417826011932af Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/52689 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Aurelien Degremont <adegremont@nvidia.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-12998 mds: add no_create parameter to stop creates Add an target tunable parameter and mount option "no_create" to disable new *directory* creation on an MDT. This sends the flag OS_STATFS_NOCREATE to the clients, and the DNE MDT space balance will avoid selecting that MDT when creating a new subdirectory, without disabling access to existing files/dirs. This allows "soft disabling" an MDT in advance of storage upgrades to minimize new directories and files created on that MDT, reduce future migration, and/or backup/restore workload. As yet it does not totally disable *file* creation on the MDT, but it may be extended to do so in the future. This is analogous to the "no_precreate" option that was added on the OSTs, and "no_create" has been added to the OSTs for consistency ("no_precreate" is kept for compatibility for now). Test-Parameters: testlist=conf-sanity env=ONLY=112b,ONLY_REPEAT=50 Signed-off-by: Andreas Dilger <adilger@whamcloud.com> Signed-off-by: Lai Siyao <lai.siyao@whamcloud.com> Change-Id: I53cfb48ade2f844b18bfc630e7fcea6de9ce7057 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/47124 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Hongchao Zhang <hongchao@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-17188 mdt: remove n from LDLM_DEBUG LDLM_DEBUG() doesn't need n in an extra message Test-Parameters: trivial Signed-off-by: Alex Zhuravlev <bzzz@whamcloud.com> Change-Id: I5a62cccb0a17b3f878206e8bbec6c1fbe07c4753 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/52673 Reviewed-by: Patrick Farrell <pfarrell@whamcloud.com> Reviewed-by: Lai Siyao <lai.siyao@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com>
LU-15246 ptlrpc: per-device adaptive timeout parameters When a client is mounting multiple filesystems with different MGSes setting global parameters at_min, at_max, etc., then the settings from one filesystem's MGS config will also apply to RPCs sent for the OSC, MDC, and MGC devices on the other filesystem(s). Typically the settings of the last filesystem to mount on the client override the earlier values, and there is no way to separate them. Moving the parameters to be per-device values allows them to be set independently for each set of client devices, so that the client can interact properly with each set of servers. This allows e.g. different timeouts for local and remote mounts, or for flash and HDD filesystems that have different load and performance. Add per-device adaptive timeout parameters that can optionally replace global parameters of the same name: at_min -> *.<fsname>*.at_min at_max -> *.<fsname>*.at_max at_history -> *.<fsname>*.at_history ldlm_enqeue_min -> *.<fsname>*.ldlm_enqueue_min These parameters should always be set with fsname in the device name, rather than pure wildcard '*' device names, or it will be be same as the global parameters in the end (settings from one MGS will apply to devices on other filesystems). That is a bug in how "lctl set_param -P" works, but will be fixed separately. Signed-off-by: Lei Feng <flei@whamcloud.com> Change-Id: I5b04c9aa53a446fb5a78bfaff372b4f236c9eb8a Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/45598 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Mikhail Pershin <mpershin@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-17015 obdclass: set cache entry/acquire expiry at init Give the ability to define values for cache entry expire and acquire expire directly at upcall cache init. Test-Parameters: trivial Signed-off-by: Sebastien Buisson <sbuisson@ddn.com> Change-Id: Iee0dea66943ab6747d85a378861ae98c29faa11a Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/52271 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Reviewed-by: Aurelien Degremont <adegremont@nvidia.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
LU-10499 pcc: use foreign layout for PCCRO on server side This patch includes the codes about using foreign layout for PCCRO on the server side (LOD|MDD|MDT layers). Signed-off-by: Qian Yingjin <qian@ddn.com> Change-Id: I48467be9fef54bd05432528b685241aa53978d24 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/51375 Reviewed-by: James Simmons <jsimmons@infradead.org> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com>
LU-17015 obdclass: make upcall cache hashtable size dynamic The hash table used by the upcall cache mechanism should have an adjustable size, depending on the purpose and context where it is used. Signed-off-by: Sebastien Buisson <sbuisson@ddn.com> Change-Id: I53c5cb14f9a5630fc269d97cead9a5ca6a33895e Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/52128 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Aurelien Degremont <adegremont@nvidia.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>