[LU-17030] allow setting max_cached_mb with % Created: 15/Aug/23  Updated: 02/Nov/23  Resolved: 31/Aug/23

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.16.0

Type: Improvement Priority: Minor
Reporter: Patrick Farrell Assignee: Patrick Farrell
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by LU-16757 Allow max_cached_mb to be set as a pe... Resolved
Related
is related to LU-16749 apply a filter to the configuration log. Open
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

Lustre's max_cached_mb parameter is challenging because it must be set to a specific numeric value, so in effect it cannot be set on the server side unless all clients are guaranteed identical.

Let's add the ability to set that to a % of memory to make it more useful.

 Comments   
Comment by Gerrit Updater [ 15/Aug/23 ]

"Patrick Farrell <pfarrell@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/51952
Subject: LU-17030 llite: allow setting max_cached_mb to a %
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 928753ecbc8ac656dd98bfa56483c02c9f2c2aa5

Comment by Gerrit Updater [ 31/Aug/23 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/51952/
Subject: LU-17030 llite: allow setting max_cached_mb to a %
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: e40be984009b2ae4efe13a19e3acf3cd9e183124

Comment by Patrick Farrell [ 31/Aug/23 ]

Merged

Generated at Sat Feb 10 03:32:01 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.