From: Christoph Hellwig <hch@lst.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mike Marshall <hubcap@omnibond.com>,
Al Viro <viro@zeniv.linux.org.uk>, Christoph Hellwig <hch@lst.de>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Boaz Harrosh <ooo@electrozaur.com>,
Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: [GIT PULL] Orangefs (text only resend)
Date: Sun, 6 Sep 2015 08:35:52 +0200 [thread overview]
Message-ID: <20150906063552.GA7224@lst.de> (raw)
In-Reply-To: <CA+55aFwE-sVT0CUquKKz8=SR=fomJih51Z44NjqiuwejpNWnuw@mail.gmail.com>
Hi Linus,
sorry, I've been away from mail for a few days.
I've been pretty happy with the code when I looked over it, which
was a while ago.
On Wed, Sep 02, 2015 at 04:34:41PM -0700, Linus Torvalds wrote:
> (a) the iovecs are walked manually (eg
> pvfs_bufmap_copy_to_user_iovec()). I would really want to see the code
> use the iov_iter infrastructure
And that was before we had the full blown iov_iter code. Note that
orangefs always does O_DIRECT-style I/O and doesn't go through the
page cache or does any other similar client side caching except for mmap,
so it will only use the low-level iov_iter helpers.
> - naming is an odd mix of "orangefs" and "pvfs2", both in the code
> and in the filenames.
I found this a bit odd to - pvfs2 was the original version and now
Clemson has done orangefs based on it. Mike might have more comments
on why he wants to keep both names.
> I'd also like to have more of an idea of who expects to maintain this?
> I'm assuming that's Mark (and omnibond?), but it would be good to hear
> who the users are and what the long-term support is supposed to be. We
> have had a tradition of filesystems that don't then get used very
> much, and they bit-rot.
PVFS2 has been around forever, and orangefs for quite a while. I know
Mike has been working on getting this in shape for a couple years, and
been good at fixing review feedback.
next prev parent reply other threads:[~2015-09-06 6:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 15:42 [GIT PULL] Orangefs (text only resend) Mike Marshall
2015-09-02 23:34 ` Linus Torvalds
2015-09-03 1:13 ` Mike Marshall
2015-09-03 1:28 ` Linus Torvalds
2015-09-03 20:22 ` Linus Torvalds
2015-09-03 22:18 ` Mike Marshall
2015-09-03 22:44 ` Greg Kroah-Hartman
2015-09-06 6:35 ` Christoph Hellwig [this message]
2015-09-06 9:08 ` Al Viro
2015-09-06 14:52 ` Mike Marshall
2015-09-06 15:00 ` Mike Marshall
2015-09-06 20:20 ` Al Viro
2015-09-07 6:37 ` Al Viro
2015-09-07 21:10 ` Mike Marshall
2015-09-07 23:22 ` Al Viro
2015-09-08 0:47 ` Theodore Ts'o
2015-09-08 2:49 ` Dave Chinner
2015-09-08 14:48 ` Christoph Hellwig
2015-09-08 18:21 ` Mike Marshall
2015-09-09 15:05 ` Mike Marshall
2015-09-11 21:12 ` Mike Marshall
2015-09-11 22:24 ` Al Viro
2015-09-13 11:56 ` Mike Marshall
2015-09-11 23:20 ` Linus Torvalds
2015-09-13 11:59 ` Mike Marshall
2015-09-06 14:35 ` Mike Marshall
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=20150906063552.GA7224@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ooo@electrozaur.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).