From: Trond Myklebust <trondmy@primarydata.com>
To: "lsf-pc@lists.linux-foundation.org" <lsf-pc@lists.linux-foundation.org>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: [LSF/MM TOPIC] Performance of seekdir(SEEK_HOLE/DATA) and FIEMAP
Date: Thu, 16 Mar 2017 16:09:01 +0000 [thread overview]
Message-ID: <1489680539.3151.3.camel@primarydata.com> (raw)
Hi all,
If there are any free slots on the filesystem track, then it would be
nice to have a conversation about use of FIEMAP and SEEK_HOLE/DATA
performance.
The issue is this: as large sparse files become more prevalent, there
is a potential performance advantage to be made if applications can
quickly and easily detect areas of no data.
Full disclosure: my interest here is seeing Anna's work on implementing
the NFSv4.2 sparse file support come to fruition; right now she is
finding that the performance of the filesystem tools (both seekdir()
and FIEMAP) are insufficient to allow us to implement the READPLUS (htt
ps://tools.ietf.org/html/rfc7862#section-6.2.1) operation and realise
the promised performance goals.
If there is time left on the schedule, then it might be nice to have a
full discussion of this topic with all the filesystem folks present,
but if not, we could do it as a lightning talk.
Thanks
Trond
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com
next reply other threads:[~2017-03-16 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 16:09 Trond Myklebust [this message]
2017-03-16 17:53 ` [Lsf-pc] [LSF/MM TOPIC] Performance of seekdir(SEEK_HOLE/DATA) and FIEMAP Jeff Layton
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=1489680539.3151.3.camel@primarydata.com \
--to=trondmy@primarydata.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).