public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Zach Brown <zab@redhat.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-nfs@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [LSF/MM TOPIC] copy offloading
Date: Wed, 15 Jan 2014 15:10:55 -0800	[thread overview]
Message-ID: <1389827455.5567.602.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <20140115202754.GL8102@lenny.home.zabbo.net>

On Wed, 2014-01-15 at 12:27 -0800, Zach Brown wrote:
> Discussing copy offloading at LSF is appropriate because it can involve
> so many layers of the stack:
> 
>  - high level syscall interface
>  - in-kernel high level entry point for nfsd 
>  - fs specific implementations (btrfs and ocfs2 cow, nfs) 
>  - vfs helper for offloading block copies for ext*,xfs
>  - bio offload requests for cow block devices like bcache/dm-cache
>  - encoding offload bios into scsi reqs
>  - processing virt guest device offload requests with host syscalls
> 
> Getting the user and in-kernel interfaces right to support all these
> moving parts has proven tricky.  The more input, the better.
> 
> It's been a while since I sent out a refreshed version of the series.
> That'll be remedied before LSF rolls around :). 
> 

+1

Now that EXTENDED_COPY LID1 target mode logic is upstream, I'm really
eager to start utilizing it Linux host side.  ;)

--nab


  reply	other threads:[~2014-01-15 23:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 20:27 [LSF/MM TOPIC] copy offloading Zach Brown
2014-01-15 23:10 ` Nicholas A. Bellinger [this message]
2014-01-16  0:46   ` Douglas Gilbert

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=1389827455.5567.602.camel@haakon3.risingtidesystems.com \
    --to=nab@linux-iscsi.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=zab@redhat.com \
    /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