linux.git/fs/nfs/write.c, branch v5.14

NFSv4.1 identify and mark RPC tasks that can move between transports

2021-07-08T18:03:24+00:00

In preparation for when we can re-try a task on a different transport,
identify and mark such RPC tasks as moveable. Only 4.1+ operarations can
be re-tried on a different transport.

Signed-off-by: Olga Kornievskaia 
Signed-off-by: Trond Myklebust

NFSv4: Don't modify the change attribute cached in the inode

2021-04-13T14:04:05+00:00

When the client is caching data and a write delegation is held, then the
server may send a CB_GETATTR to query the attributes. When this happens,
the client is supposed to bump the change attribute value that it
returns if it holds cached data.
However that process uses a value that is stored in the delegation. We
do not want to bump the change attribute held in the inode.

Signed-off-by: Trond Myklebust

NFS: Separate tracking of file mode cache validity from the uid/gid

2021-04-13T13:41:16+00:00

chown()/chgrp() and chmod() are separate operations, and in addition,
there are mode operations that are performed automatically by the
server. So let's track mode validity separately from the file ownership
validity.

Signed-off-by: Trond Myklebust

NFS: Replace use of NFS_INO_REVAL_PAGECACHE when checking cache validity

2021-04-13T00:11:44+00:00

When checking cache validity, be more specific than just 'we want to
check the page cache validity'. In almost all cases, we want to check
that change attribute, and possibly also the size.

Signed-off-by: Trond Myklebust

NFS: Fix open coded versions of nfs_set_cache_invalid()

2021-03-08T21:13:55+00:00

nfs_set_cache_invalid() has code to handle delegations, and other
optimisations, so let's use it when appropriate.

Signed-off-by: Trond Myklebust 
Signed-off-by: Anna Schumaker

NFS: Add support for eager writes

2021-02-16T21:11:14+00:00

Support eager writing to the server, meaning that we write the data to
cache on the server, and wait for that to complete. This ensures that we
see ENOSPC errors immediately.

Signed-off-by: Trond Myklebust 
Signed-off-by: Anna Schumaker

NFS: Optimise sparse writes past the end of file

2021-02-08T16:26:14+00:00

If we're doing a write, and the entire page lies beyond the end-of-file,
then we can assume the write can be extended to cover the beginning of
the page, since we know the data in that region will be all zeros.

Signed-off-by: Trond Myklebust 
Signed-off-by: Anna Schumaker

mm/writeback: discard NR_UNSTABLE_NFS, use NR_WRITEBACK instead

2020-06-02T17:59:08+00:00

After an NFS page has been written it is considered "unstable" until a
COMMIT request succeeds.  If the COMMIT fails, the page will be
re-written.

These "unstable" pages are currently accounted as "reclaimable", either
in WB_RECLAIMABLE, or in NR_UNSTABLE_NFS which is included in a
'reclaimable' count.  This might have made sense when sending the COMMIT
required a separate action by the VFS/MM (e.g.  releasepage() used to
send a COMMIT).  However now that all writes generated by ->writepages()
will automatically be followed by a COMMIT (since commit 919e3bd9a875
("NFS: Ensure we commit after writeback is complete")) it makes more
sense to treat them as writeback pages.

So this patch removes NR_UNSTABLE_NFS and accounts unstable pages in
NR_WRITEBACK and WB_WRITEBACK.

A particular effect of this change is that when
wb_check_background_flush() calls wb_over_bg_threshold(), the latter
will report 'true' a lot less often as the 'unstable' pages are no
longer considered 'dirty' (as there is nothing that writeback can do
about them anyway).

Currently wb_check_background_flush() will trigger writeback to NFS even
when there are relatively few dirty pages (if there are lots of unstable
pages), this can result in small writes going to the server (10s of
Kilobytes rather than a Megabyte) which hurts throughput.  With this
patch, there are fewer writes which are each larger on average.

Where the NR_UNSTABLE_NFS count was included in statistics
virtual-files, the entry is retained, but the value is hard-coded as
zero.  static trace points and warning printks which mentioned this
counter no longer report it.

[akpm@linux-foundation.org: re-layout comment]
[akpm@linux-foundation.org: fix printk warning]
Signed-off-by: NeilBrown 
Signed-off-by: Andrew Morton 
Reviewed-by: Jan Kara 
Reviewed-by: Christoph Hellwig 
Acked-by: Trond Myklebust 
Acked-by: Michal Hocko 	[mm]
Cc: Christoph Hellwig 
Cc: Chuck Lever 
Link: http://lkml.kernel.org/r/87d06j7gqa.fsf@notabene.neil.brown.name
Signed-off-by: Linus Torvalds

NFS/pnfs: Don't use RPC_TASK_CRED_NOREF with pnfs

2020-05-13T13:55:36+00:00

When we're doing pnfs then the credential being used for the RPC call
is not necessarily the same as the one used in the open context, so
don't use RPC_TASK_CRED_NOREF.

Fixes: 612965072020 ("NFSv4: Avoid referencing the cred unnecessarily during NFSv4 I/O")
Signed-off-by: Trond Myklebust

NFS: Try to join page groups before an O_DIRECT retransmission

2020-04-01T17:37:57+00:00

If we have to retransmit requests, try to join their page groups
first.

Signed-off-by: Trond Myklebust