From: Jorge Mora <jmora1300@gmail.com>
To: linux-nfs@vger.kernel.org
Cc: trond.myklebust@hammerspace.com, Anna.Schumaker@netapp.com
Subject: [PATCH v1 0/2] add support for IO_ADVISE
Date: Tue, 10 Jan 2023 11:46:39 -0700 [thread overview]
Message-ID: <20230110184641.13334-1-mora@netapp.com> (raw)
Adds support for using the NFS v4.2 operation IO_ADVISE to
send client I/O access pattern hints to the server.
There is a one-to-one correspondence between the advice
(POSIX_FADV_*) given in fadvise64() and the bitmap mask sent
to the server. Any other advice given, results in just
calling generic_fadvise().
The bitmap mask given by the server reply is just ignored
since the fadvise64() returns 0 on success. If server
replies with more than one bitmap word, only the first word
is stored on the nfs42_io_advise_res struct and all other
words are ignored.
Added trace point (nfs4_io_advise) for this operation:
nfs4_io_advise: error=0 (OK) fileid=00:32:4217220 \
fhandle=0x4a271991 stateid=0:0x30b83748 offset=0 \
count=200 arg_hints=SEQUENTIAL res_hints=SEQUENTIAL
Jorge Mora (2):
NFS: add IO_ADVISE operation
NFSv4.2 add tracepoint to IO_ADVISE
fs/nfs/nfs42.h | 1 +
fs/nfs/nfs42proc.c | 68 +++++++++++++++++++++++++++++++
fs/nfs/nfs42xdr.c | 84 +++++++++++++++++++++++++++++++++++++++
fs/nfs/nfs4file.c | 37 +++++++++++++++++
fs/nfs/nfs4proc.c | 1 +
fs/nfs/nfs4trace.h | 75 ++++++++++++++++++++++++++++++++++
fs/nfs/nfs4xdr.c | 1 +
include/linux/nfs4.h | 1 +
include/linux/nfs_fs_sb.h | 1 +
include/linux/nfs_xdr.h | 28 +++++++++++++
10 files changed, 297 insertions(+)
--
2.31.1
next reply other threads:[~2023-01-10 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 18:46 Jorge Mora [this message]
2023-01-10 18:46 ` [PATCH v1 1/2] NFS: add IO_ADVISE operation Jorge Mora
2023-01-10 20:33 ` Trond Myklebust
2023-01-10 18:46 ` [PATCH v1 2/2] NFSv4.2 add tracepoint to IO_ADVISE Jorge Mora
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230110184641.13334-1-mora@netapp.com \
--to=jmora1300@gmail.com \
--cc=Anna.Schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.