[LU-13786] Take server-side locks for direct i/o Created: 14/Jul/20 Updated: 15/Jul/20 Resolved: 15/Jul/20 |
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Alexander Zarochentsev | Assignee: | WC Triage |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||
| Severity: | 3 | ||||||||||||||||
| Bugzilla ID: | 18,801 | ||||||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||||||
| Description |
|
Trying to investigate an idea that client side locks are not needed for direct i/o, formally, there is no client cache to protect, and client locks are expanded at server to the maximum extent while server-side locks are not (part of lock-ahead patch). The improvement was initially implemented for Luste-1.8 (https://bugzilla.lustre.org/show_bug.cgi?id=18801) and lost during client re-write (CLIO). |
| Comments |
| Comment by Gerrit Updater [ 14/Jul/20 ] |
|
Alexander Zarochentsev (alexander.zarochentsev@hpe.com) uploaded a new patch: https://review.whamcloud.com/39363 |
| Comment by Alexander Zarochentsev [ 15/Jul/20 ] |
|
Closing as a dup of |