diff options
| author |   Trond Myklebust <trondmy@gmail.com> | 2019-09-22 15:07:49 -0400 |
|---|---|---|
| committer |   Anna Schumaker <Anna.Schumaker@Netapp.com> | 2019-09-24 15:58:20 -0400 |
| commit | c128e575514ce93dced349417d136304a33b6f99 (patch) | |
| tree | de3b205b0a419093b51f9e5184dcad567da0d84f /drivers/gpu/drm/i915/gt/intel_workarounds.h | |
| parent | NFSv4: Handle NFS4ERR_OLD_STATEID in LOCKU (diff) | |
| download | linux-dev-c128e575514ce93dced349417d136304a33b6f99.tar.xz linux-dev-c128e575514ce93dced349417d136304a33b6f99.zip | |
NFS: Optimise the default readahead size
In the years since the max readahead size was fixed in NFS, a number of
things have happened:
- Users can now set the value directly using /sys/class/bdi
- NFS max supported block sizes have increased by several orders of
magnitude from 64K to 1MB.
- Disk access latencies are orders of magnitude faster due to SSD + NVME.
In particular note that if the server is advertising 1MB as the optimal
read size, as that will set the readahead size to 15MB.
Let's therefore adjust down, and try to default to VM_READAHEAD_PAGES.
However let's inform the VM about our preferred block size so that it
can choose to round up in cases where that makes sense.
Reported-by: Alkis Georgopoulos <alkisg@gmail.com>
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'drivers/gpu/drm/i915/gt/intel_workarounds.h')
0 files changed, 0 insertions, 0 deletions