[LU-4933] Automatically tune the max_dirty_mb Created: 21/Apr/14 Updated: 13/Oct/15 Resolved: 01/Jul/14 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.6.0, Lustre 2.5.4 |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Li Xi (Inactive) | Assignee: | Hongchao Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | patch | ||
| Issue Links: |
|
||||||||||||
| Rank (Obsolete): | 13637 | ||||||||||||
| Description |
|
When RPC size or the max RPCs in flight is increased, the actual limit might be max_dirty_mb value. That is confusing. We could be able to tune that value automatically. |
| Comments |
| Comment by Li Xi (Inactive) [ 21/Apr/14 ] |
|
Please check this patch: |
| Comment by Peter Jones [ 21/Apr/14 ] |
|
Hongchao Could you please review this patch? Thanks Peter |
| Comment by Hongchao Zhang [ 26/May/14 ] |
|
the updated patch is tracked at http://review.whamcloud.com/#/c/10446/ |
| Comment by Peter Jones [ 01/Jul/14 ] |
|
Landed for 2.6 |
| Comment by Li Xi (Inactive) [ 02/Jul/14 ] |
|
Backported for b2_5: |