From: Joel Becker <Joel.Becker@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [GIT PULL] ocfs2 changes for 2.6.32
Date: Mon, 14 Sep 2009 15:14:35 -0700 [thread overview]
Message-ID: <20090914221434.GA4507@mail.oracle.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0909141417180.4950@localhost.localdomain>
On Mon, Sep 14, 2009 at 02:32:36PM -0700, Linus Torvalds wrote:
> On Fri, 11 Sep 2009, Joel Becker wrote:
> >
> > Linus, et al,
> > Here are the ocfs2 feature changes for 2.6.32. The big ticket
> > item is the reflinkat(2) system call and ocfs2's support for it. The
> > ocfs2 support accounts for all but a handful of the changes. The
> > remaining few patches are fixes.
>
> I _really_ want some kind of ack's for new filesystem system calls like
> this. I'm not going to pull a new 'reflink[at]()' system call just based
> on a single filesystem.
I'll get specific acks. I sent it via ocfs2.git because others
recommended I not send it upstream in June but instead wait until
I had at least one filesystem implementing it.
> Yes, there's clearly been _some_ discussion, but (a) I've not seen it
> (since it's been on 'fsdevel', which is one of those single-topic mailing
> lists that I'm totally uninterested in, since they tend to become clique
> groups) and (b) you don't even say whether the thing has been acked by
> things like the security angle etc.
Fair enough. Don't worry, the security folks were involved.
I'll get direct acks.
> I also don't understand why it's called 'reflink'. Why not 'copyfile'? We
> should not name things by implementation, we should name things by what
> they _do_. And I'm not seeing what is so 'reflink' about this that it's
> not a 'copyfile'. I also am not entirely clear on why you need the source
> name, and not - for example - an 'fd'.
>
> Are we going to add 'freflink[at]()' at some point?
It's a link(2) analogue. symlink(2) has the loosest coupling,
and reflink(2) the highest. We're not going to add freflink[at]().
It's a snap, not a copy. It can be used to implement a copy, and
copyfile() in libc can be written with reflinkat(2), but it isn't just a
copy.
Joel
--
"There is shadow under this red rock.
(Come in under the shadow of this red rock)
And I will show you something different from either
Your shadow at morning striding behind you
Or your shadow at evening rising to meet you.
I will show you fear in a handful of dust."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
WARNING: multiple messages have this Message-ID (diff)
From: Joel Becker <Joel.Becker@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [GIT PULL] ocfs2 changes for 2.6.32
Date: Mon, 14 Sep 2009 15:14:35 -0700 [thread overview]
Message-ID: <20090914221434.GA4507@mail.oracle.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0909141417180.4950@localhost.localdomain>
On Mon, Sep 14, 2009 at 02:32:36PM -0700, Linus Torvalds wrote:
> On Fri, 11 Sep 2009, Joel Becker wrote:
> >
> > Linus, et al,
> > Here are the ocfs2 feature changes for 2.6.32. The big ticket
> > item is the reflinkat(2) system call and ocfs2's support for it. The
> > ocfs2 support accounts for all but a handful of the changes. The
> > remaining few patches are fixes.
>
> I _really_ want some kind of ack's for new filesystem system calls like
> this. I'm not going to pull a new 'reflink[at]()' system call just based
> on a single filesystem.
I'll get specific acks. I sent it via ocfs2.git because others
recommended I not send it upstream in June but instead wait until
I had at least one filesystem implementing it.
> Yes, there's clearly been _some_ discussion, but (a) I've not seen it
> (since it's been on 'fsdevel', which is one of those single-topic mailing
> lists that I'm totally uninterested in, since they tend to become clique
> groups) and (b) you don't even say whether the thing has been acked by
> things like the security angle etc.
Fair enough. Don't worry, the security folks were involved.
I'll get direct acks.
> I also don't understand why it's called 'reflink'. Why not 'copyfile'? We
> should not name things by implementation, we should name things by what
> they _do_. And I'm not seeing what is so 'reflink' about this that it's
> not a 'copyfile'. I also am not entirely clear on why you need the source
> name, and not - for example - an 'fd'.
>
> Are we going to add 'freflink[at]()' at some point?
It's a link(2) analogue. symlink(2) has the loosest coupling,
and reflink(2) the highest. We're not going to add freflink[at]().
It's a snap, not a copy. It can be used to implement a copy, and
copyfile() in libc can be written with reflinkat(2), but it isn't just a
copy.
Joel
--
"There is shadow under this red rock.
(Come in under the shadow of this red rock)
And I will show you something different from either
Your shadow at morning striding behind you
Or your shadow at evening rising to meet you.
I will show you fear in a handful of dust."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2009-09-14 22:14 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 20:04 [Ocfs2-devel] [GIT PULL] ocfs2 changes for 2.6.32 Joel Becker
2009-09-11 20:04 ` Joel Becker
2009-09-14 21:32 ` [Ocfs2-devel] " Linus Torvalds
2009-09-14 21:32 ` Linus Torvalds
2009-09-14 22:14 ` Joel Becker [this message]
2009-09-14 22:14 ` Joel Becker
2009-09-14 23:27 ` [Ocfs2-devel] " Linus Torvalds
2009-09-14 23:27 ` Linus Torvalds
2009-09-15 0:04 ` [Ocfs2-devel] " Joel Becker
2009-09-15 0:04 ` Joel Becker
2009-09-15 0:31 ` [Ocfs2-devel] " Linus Torvalds
2009-09-15 0:31 ` Linus Torvalds
2009-09-15 0:54 ` [Ocfs2-devel] " Joel Becker
2009-09-15 0:54 ` Joel Becker
2009-09-15 2:01 ` [Ocfs2-devel] " Linus Torvalds
2009-09-15 2:01 ` Linus Torvalds
2009-09-15 4:05 ` [Ocfs2-devel] " Arjan van de Ven
2009-09-15 4:05 ` Arjan van de Ven
2009-09-15 4:35 ` [Ocfs2-devel] " Joel Becker
2009-09-15 4:35 ` Joel Becker
2009-09-15 4:06 ` [Ocfs2-devel] " Joel Becker
2009-09-15 4:06 ` Joel Becker
2009-09-15 16:30 ` [Ocfs2-devel] " Linus Torvalds
2009-09-15 16:30 ` Linus Torvalds
2009-09-15 21:45 ` [Ocfs2-devel] " Joel Becker
2009-09-15 21:45 ` Joel Becker
2009-09-16 4:20 ` [Ocfs2-devel] " Linus Torvalds
2009-09-16 4:20 ` Linus Torvalds
2009-09-16 4:40 ` [Ocfs2-devel] " Joel Becker
2009-09-16 4:40 ` Joel Becker
2009-09-17 16:29 ` [Ocfs2-devel] " Linus Torvalds
2009-09-17 16:29 ` Linus Torvalds
2009-09-17 16:38 ` [Ocfs2-devel] " Arjan van de Ven
2009-09-17 16:38 ` Arjan van de Ven
2009-09-17 20:16 ` [Ocfs2-devel] " Linus Torvalds
2009-09-17 20:16 ` Linus Torvalds
2009-09-17 18:40 ` [Ocfs2-devel] " Roland Dreier
2009-09-17 18:40 ` Roland Dreier
2009-09-17 20:17 ` [Ocfs2-devel] " Linus Torvalds
2009-09-17 20:17 ` Linus Torvalds
2009-09-17 20:34 ` [Ocfs2-devel] " Joel Becker
2009-09-17 20:34 ` Joel Becker
2009-09-18 0:29 ` [Ocfs2-devel] " Linus Torvalds
2009-09-18 0:29 ` Linus Torvalds
2009-09-17 20:42 ` [Ocfs2-devel] " Roland Dreier
2009-09-17 20:42 ` Roland Dreier
2009-09-17 20:55 ` [Ocfs2-devel] " Linus Torvalds
2009-09-17 20:55 ` Linus Torvalds
2009-09-18 1:43 ` [Ocfs2-devel] " Joel Becker
2009-09-18 1:43 ` Joel Becker
2009-09-18 13:34 ` Pádraig Brady
2009-09-18 13:34 ` Pádraig Brady
2009-09-18 18:37 ` Joel Becker
2009-09-18 18:37 ` Joel Becker
2009-09-18 17:23 ` Peter W. Morreale
2009-09-18 17:23 ` Peter W. Morreale
2009-09-18 18:39 ` Joel Becker
2009-09-18 18:39 ` Joel Becker
2009-09-15 6:44 ` Miklos Szeredi
2009-09-15 6:44 ` Miklos Szeredi
2009-09-23 11:02 ` [Ocfs2-devel] [GIT PULL] ocfs2 changes for 2.6.32 (take 2, no syscall) Joel Becker
2009-09-23 11:02 ` Joel Becker
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=20090914221434.GA4507@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=torvalds@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 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.