linux-stable.git/include/linux/nfs_fs.h, branch v4.10.2

NFS: Clean up nfs_attribute_timeout()

2016-12-19T22:29:44+00:00

It can be made static.

Signed-off-by: Trond Myklebust

NFS: Remove unused function nfs_revalidate_inode_rcu()

2016-12-19T22:29:41+00:00

Signed-off-by: Trond Myklebust

NFS: Only look at the change attribute cache state in nfs_check_verifier

2016-12-04T23:34:34+00:00

When looking at whether or not our dcache is valid, we really don't care
about the general state of the directory attribute cache. Instead, we
we only care about the state of the change attribute.

This fixes a performance issue when the client is responsible for
changing the directory contents; a number of NFSv4 operations will
atomically update the directory change attribute, but may not return
all the other attributes.

Signed-off-by: Trond Myklebust

NFS: discard nfs_lockowner structure.

2016-12-01T22:58:13+00:00

It now has only one field and is only used in one structure.
So replaced it in that structure by the field it contains.

Signed-off-by: NeilBrown 
Reviewed-by: Jeff Layton 
Signed-off-by: Trond Myklebust

NFSv4: add flock_owner to open context

2016-12-01T22:57:27+00:00

An open file description (struct file) in a given process can be
associated with two different lock owners.

It can have a Posix lock owner which will be different in each process
that has a fd on the file.
It can have a Flock owner which will be the same in all processes.

When searching for a lock stateid to use, we need to consider both of these
owners

So add a new "flock_owner" to the "nfs_open_context" (of which there
is one for each open file description).

This flock_owner does not need to be reference-counted as there is a
1-1 relation between 'struct file' and nfs open contexts,
and it will never be part of a list of contexts.  So there is no need
for a 'flock_context' - just the owner is enough.

The io_count included in the (Posix) lock_context provides no
guarantee that all read-aheads that could use the state have
completed, so not supporting it for flock locks in not a serious
problem.  Synchronization between flock and read-ahead can be added
later if needed.

When creating an open_context for a non-openning create call, we don't have
a 'struct file' to pass in, so the lock context gets initialized with
a NULL owner, but this will never be used.

The flock_owner is not used at all in this patch, that will come later.

Acked-by: Jeff Layton 
Signed-off-by: NeilBrown 
Reviewed-by: Jeff Layton 
Signed-off-by: Trond Myklebust

NFS: remove l_pid field from nfs_lockowner

2016-12-01T22:57:07+00:00

this field is not used in any important way and probably should
have been removed by

Commit: 8003d3c4aaa5 ("nfs4: treat lock owners as opaque values")

which removed the pid argument from nfs4_get_lock_state.

Except in unusual and uninteresting cases, two threads with the same
->tgid will have the same ->files pointer, so keeping them both
for comparison brings no benefit.

Acked-by: Jeff Layton 
Signed-off-by: NeilBrown 
Reviewed-by: Jeff Layton 
Signed-off-by: Trond Myklebust

NFS: Remove unused function nfs_revalidate_mapping_protected()

2016-07-05T23:11:05+00:00

Clean up...

Signed-off-by: Trond Myklebust

NFS: Do not serialise O_DIRECT reads and writes

2016-07-05T23:11:04+00:00

Allow dio requests to be scheduled in parallel, but ensuring that they
do not conflict with buffered I/O.

Signed-off-by: Trond Myklebust

NFS: Kill NFS_INO_NFS_INO_FLUSHING: it is a performance killer

2016-06-22T13:59:42+00:00

filemap_datawrite() and friends already deal just fine with livelock.

Signed-off-by: Trond Myklebust

Merge branch 'work.preadv2' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs

2016-05-17T22:05:23+00:00

Pull vfs cleanups from Al Viro:
 "More cleanups from Christoph"

* 'work.preadv2' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs:
  nfsd: use RWF_SYNC
  fs: add RWF_DSYNC aand RWF_SYNC
  ceph: use generic_write_sync
  fs: simplify the generic_write_sync prototype
  fs: add IOCB_SYNC and IOCB_DSYNC
  direct-io: remove the offset argument to dio_complete
  direct-io: eliminate the offset argument to ->direct_IO
  xfs: eliminate the pos variable in xfs_file_dio_aio_write
  filemap: remove the pos argument to generic_file_direct_write
  filemap: remove pos variables in generic_file_read_iter