[LU-7896] lu_object_limit() is called too frequently Created: 22/Mar/16 Updated: 13/Feb/19 Resolved: 22/Jun/16 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.9.0 |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Alex Zhuravlev | Assignee: | Alex Zhuravlev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||||||||||
| Description |
|
with ZFS the number of objects in LU cache is limited, so any lu_object_new() checks whether the limit is exceeded. so, at some point it's called for every new object and worse - many threads got blocked in lu_site_purge() due to that. we don't need that strong semantics for the number of cached object, this should be fixed in a way to purge objects in batches in non-blocking manner. |
| Comments |
| Comment by Gerrit Updater [ 23/Mar/16 ] |
|
Alex Zhuravlev (alexey.zhuravlev@intel.com) uploaded a new patch: http://review.whamcloud.com/19082 |
| Comment by Gerrit Updater [ 22/Jun/16 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/19082/ |
| Comment by Joseph Gmitter (Inactive) [ 22/Jun/16 ] |
|
Landed to master for 2.9.0 |