Whamcloud - gitweb
LU-13363 lod: do object allocation in OST pool
authorSigned-off-by: Emoly Liu <emoly@whamcloud.com>
Thu, 14 Apr 2022 16:04:24 +0000 (12:04 -0400)
committerAndreas Dilger <adilger@whamcloud.com>
Thu, 16 Jun 2022 20:25:57 +0000 (20:25 +0000)
commitf71b7547b63842d0c3d448ab77d8ab07f0dd3d2a
treefe434d186effadbe96b51ace70fd725eebd23bb4
parent9623a16d3f5984d9b72cb8defc5821b3d8658acc
LU-13363 lod: do object allocation in OST pool

Currently, the ltd->ltd_qos.lq_same_space boolean that decides
whether the LOD QOS allocator is active for an allocation or not
is tracked for the entire LOV. But when a pool is specified, this
judgement should be tracked on a per-pool basis.

sanity.sh test_116c is added to verify this patch.

Lustre-change: https://review.whamcloud.com/38136
Lustre-commit: e642e75cde0248eee30ca94aaeb81653db7f8d03

Test-Parameters: ostcount=6 testlist=sanity env=ONLY=116c
Signed-off-by: Emoly Liu <emoly@whamcloud.com>
Change-Id: I463d5927c7a9c9171483615d2cec629ec10dc666
Reviewed-on: https://review.whamcloud.com/47334
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
lustre/lod/lod_internal.h
lustre/lod/lod_pool.c
lustre/lod/lod_qos.c
lustre/tests/conf-sanity.sh
lustre/tests/sanity.sh
lustre/tests/test-framework.sh