From: Mikulas Patocka <mpatocka@redhat.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Matthew Wilcox <willy@infradead.org>,
Zhongwei Cai <sunrise_l@sjtu.edu.cn>,
Mingkai Dong <mingkaidong@gmail.com>,
Dan Williams <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>, Dave Chinner <david@fromorbit.com>,
Theodore Ts'o <tytso@mit.edu>,
David Laight <David.Laight@aculab.com>,
Steven Whitehouse <swhiteho@redhat.com>,
Eric Sandeen <esandeen@redhat.com>,
Wang Jianchao <jianchao.wan9@gmail.com>,
Rajesh Tadakamadla <rajesh.tadakamadla@hpe.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: [RFC v3] nvfs: a filesystem for persistent memory
Date: Mon, 15 Feb 2021 10:03:54 -0500 (EST) [thread overview]
Message-ID: <alpine.LRH.2.02.2102021307370.4109@file01.intranet.prod.int.rdu2.redhat.com> (raw)
Hi
I announce a new version of NVFS - a filesystem for persistent memory.
http://people.redhat.com/~mpatocka/nvfs/
git://leontynka.twibright.com/nvfs.git
Changes since the last release:
I reworked file read/write handling:
* the functions nvfs_read and nvfs_write were deleted beacause it's
unlikely that the upstream kernel will allow them.
* the functions nvfs_read_iter and nvfs_write_iter have a fast path if
there is just one segment in iov_iter - they will call nvfs_read_locked
and nvfs_write_locked directly. This improves performance by 3% on the
read path and 1% on the write path.
* read_iter_locked uses copy_to_iter as suggested by Al Viro.
* write_iter_locked doesn't use copy_from_iter_flushcache, because we need
copy that doesn't advance the iter (the "copy" and "advance" must be two
separate operations). So, I added new operations "iov_iter_map" and
"iov_iter_unmap" - iov_iter_map will map the first segment of iov and
iov_iter_unmap will unmap it.
Do you think that introducing "iov_iter_map" and "iov_iter_unmap" is
appropriate? Do you have some other idea how to handle it?
Mikukas
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
reply other threads:[~2021-02-15 15:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LRH.2.02.2102021307370.4109@file01.intranet.prod.int.rdu2.redhat.com \
--to=mpatocka@redhat.com \
--cc=David.Laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@fromorbit.com \
--cc=esandeen@redhat.com \
--cc=jack@suse.cz \
--cc=jianchao.wan9@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mingkaidong@gmail.com \
--cc=rajesh.tadakamadla@hpe.com \
--cc=sunrise_l@sjtu.edu.cn \
--cc=swhiteho@redhat.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=vishal.l.verma@intel.com \
--cc=willy@infradead.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 read-only IMAP folder(s) and NNTP newsgroup(s).