All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: "Loke, Chetan" <Chetan.Loke@netscout.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	linux-scsi@vger.kernel.org,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Hannes Reinecke <hare@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-nfs@vger.kernel.org, Joel Becker <jlbec@evilplan.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: copy offload support in Linux - new system call needed?
Date: Thu, 15 Dec 2011 12:55:42 -0500	[thread overview]
Message-ID: <4EEA349E.8060800@redhat.com> (raw)
In-Reply-To: <D3F292ADF945FB49B35E96C94C2061B91516E489@nsmail.netscout.com>

On 12/15/2011 12:31 PM, Loke, Chetan wrote:
>> I think that hypervisor vendors will be very interested in this feature
>> which
>> would explain why vmware was active in drafting both the NFS and T10
> Specs are the only way to convince storage-target-vendors ;). Otherwise target-stack will need to implement multiple custom-CDB-handlers for different front-end APIs(which is ugly).
>
>
> Chetan

Hi Chetan,

I should post from my "Red Hat" email to make this less confusing for you - I 
know that this is in fact interesting to vendors :)

Thanks!

Ric


  reply	other threads:[~2011-12-15 17:58 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 19:22 copy offload support in Linux - new system call needed? Ric Wheeler
2011-12-14 19:22 ` Ric Wheeler
2011-12-14 19:27 ` Al Viro
2011-12-14 19:42   ` Ric Wheeler
2011-12-14 19:42     ` Ric Wheeler
2011-12-14 22:27     ` J. Bruce Fields
2011-12-14 22:27       ` J. Bruce Fields
2011-12-15 14:59       ` Trond Myklebust
2011-12-15 15:52         ` Chris Mason
2011-12-15 16:00           ` Trond Myklebust
2011-12-15 16:00             ` Trond Myklebust
2011-12-15 16:03           ` Jeff Layton
2011-12-15 16:03             ` Jeff Layton
2011-12-15 16:06             ` Trond Myklebust
2011-12-15 16:06               ` Trond Myklebust
2011-12-15 16:16               ` Jeff Layton
2011-12-15 16:16                 ` Jeff Layton
2011-12-15 16:38                 ` Trond Myklebust
2011-12-15 16:08         ` Loke, Chetan
2011-12-15 16:08           ` Loke, Chetan
2011-12-15 16:08           ` Loke, Chetan
2011-12-15 16:11           ` Trond Myklebust
2011-12-15 16:11             ` Trond Myklebust
2011-12-15 16:40             ` Loke, Chetan
2011-12-15 16:40               ` Loke, Chetan
2011-12-15 16:40               ` Loke, Chetan
2011-12-15 16:53               ` Trond Myklebust
2011-12-15 17:18                 ` Ric Wheeler
2011-12-15 17:18                   ` Ric Wheeler
2011-12-15 17:25                   ` Trond Myklebust
2011-12-15 17:31                   ` Loke, Chetan
2011-12-15 17:31                     ` Loke, Chetan
2011-12-15 17:31                     ` Loke, Chetan
2011-12-15 17:55                     ` Ric Wheeler [this message]
2011-12-15 17:27                 ` Loke, Chetan
2011-12-15 17:27                   ` Loke, Chetan
2011-12-15 17:27                   ` Loke, Chetan
2011-12-15 17:44         ` J. Bruce Fields
2011-12-15 17:44           ` J. Bruce Fields
2011-12-16  8:00     ` Joel Becker
2011-12-14 19:59 ` Jeremy Allison
2011-12-14 20:30   ` Ric Wheeler
2011-12-14 20:30     ` Ric Wheeler
2011-12-19 12:38     ` Hannes Reinecke
2011-12-19 12:38       ` Hannes Reinecke
2011-12-19 22:19   ` H. Peter Anvin
2011-12-19 22:19     ` H. Peter Anvin
2011-12-19 22:34     ` Jeremy Allison
2011-12-19 22:57     ` Dave Chinner
2011-12-19 23:29       ` H. Peter Anvin
2011-12-19 23:29         ` H. Peter Anvin

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=4EEA349E.8060800@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=Chetan.Loke@netscout.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=hare@suse.de \
    --cc=jlbec@evilplan.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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 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.