From: Roland Dreier <roland@purestorage.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] Copy offload
Date: Fri, 13 Jan 2012 11:35:38 -0800 [thread overview]
Message-ID: <CAL1RGDWJjzBnN6Aj_ngvkFco_toe8Dey5QApgmYafpEqECuTSw@mail.gmail.com> (raw)
In-Reply-To: <4F0AC112.2000709@suse.de>
In general, with my target vendor hat on, I'd be very interested in
what special SCSI commands the Linux initiator stack might want
to use. Extended copy is one (very complex) case -- and BTW
Microsoft seems to plan on using XCOPY LITE with NTFS.
Another possibly interesting example would be COMPARE AND
WRITE for clustered filesystems.
Any other storage operations that FS developers might want
from the block device? (Either standard SCSI commands or
more speculative stuff that T10 hasn't thought of yet)
- R.
next prev parent reply other threads:[~2012-01-13 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 10:27 [LSF/MM TOPIC] Copy offload Hannes Reinecke
2012-01-10 22:11 ` Joel Becker
2012-01-13 19:25 ` Martin K. Petersen
2012-01-13 19:35 ` Roland Dreier [this message]
2012-01-24 10:16 ` Boaz Harrosh
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=CAL1RGDWJjzBnN6Aj_ngvkFco_toe8Dey5QApgmYafpEqECuTSw@mail.gmail.com \
--to=roland@purestorage.com \
--cc=linux-scsi@vger.kernel.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 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).