All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ric Wheeler <ricwheeler@gmail.com>
To: "Madan, Anshul" <Anshul.Madan@netapp.com>,
	lsf10-pc@lists.linuxfoundation.org,
	linux-fsdevel@vger.kernel.org, "Lentini,
	James" <James.Lentini@netapp.com>,
	"Myklebust, Trond" <Trond.My
Subject: Re: [Lsf10-pc] [LSF/Filesystems][ATTEND]
Date: Tue, 25 May 2010 15:00:36 -0400	[thread overview]
Message-ID: <4BFC1E54.2020706@gmail.com> (raw)
In-Reply-To: <20100517222432.GC22775@mail.oracle.com>

On 05/17/2010 06:24 PM, Joel Becker wrote:
> On Mon, May 17, 2010 at 05:23:22PM -0400, Madan, Anshul wrote:
>    
>> Requesting Attendance:
>>
>> Trond Myklebust, James Lentini and Anshul Madan
>>      
> 	I (Joel Becker ) would like to request attendance to join in
> this conversation.  I'm the original proposer of reflink(2).
>
>    
>> This topic has been discussed both on Linux development mailing lists
>> [1] and at previous LSF summits. Joel Becker originally proposed a
>> syscall called reflink() that was specific to copying an inode to a
>> copy-on-write snapshot. Since then, the need for a generic copy
>> interface  that encompassed the reflink semantics as well as less
>> restrictive ones has been recognized based on discussion between Linus
>> Torvalds and Joel.
>>      
> 	My last proposal for the copyfile(2) interface is reference [2].
> I think it is a good starting point, but I'm very interested in what the
> network filesystem community has to say.  NFS's server copy capability
> is something I definitely had in mind.
>
>    
>> [1] Relevant posts:
>>
>> http://www.mail-archive.com/ocfs2-devel@oss.oracle.com/msg04347.html
>> http://www.mail-archive.com/ocfs2-devel@oss.oracle.com/msg04395.html
>>      
> Joel
>    

I think that this would be an interesting subject as well, especially 
given the mix of storage & FS people at the event.

Ric


      reply	other threads:[~2010-05-25 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.2.00.1005171556240.16844@jlentini-linux.nane.netapp.com>
2010-05-17 21:23 ` [LSF/Filesystems][ATTEND] Madan, Anshul
2010-05-17 22:24   ` [LSF/Filesystems][ATTEND] Joel Becker
2010-05-25 19:00     ` Ric Wheeler [this message]

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=4BFC1E54.2020706@gmail.com \
    --to=ricwheeler@gmail.com \
    --cc=Anshul.Madan@netapp.com \
    --cc=James.Lentini@netapp.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf10-pc@lists.linuxfoundation.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.