From: Mike Christie <mchristi@redhat.com>
To: Timofey Titovets <nefelim4ag@gmail.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: RBD Kernel: write_same_max_bytes and SCSI XCOPY
Date: Wed, 09 Dec 2015 15:37:11 -0600 [thread overview]
Message-ID: <56689F07.40502@redhat.com> (raw)
In-Reply-To: <CAGqmi77oh71KZN75Ti4k7uzp=0eujrg5vWKgLnbMvhirXuDN-A@mail.gmail.com>
On 12/09/2015 01:08 AM, Timofey Titovets wrote:
> Hi list,
> As i found write_same_max_bytes are equal to zero
> if i understand correctly, it's means what RBD not support offloading
> copy operations
>
Not yet.
I did patches to support commands like write same and compare and write
in this patchset where I made a lio rbd backend driver:
http://www.spinics.net/lists/target-devel/msg10330.html
but they were not accepted upstream.
I am currently reworking the patches to be acceptable. Some distros did
pick them up though so you might see them in there.
> Is this possible to add this feature, as example for LIO with SCSI XCOPY?
The linux kernel does yet not have xcopy support like how it supports
write same or discard. There are patches, but it has not been merged
upstream.
However, LIO does support this command by what I guess you could call
emulating it where if the underlying device does not support the command
natively then LIO will perform the operations needed. It does this for
other commands like write same too. So, even though rbd does not
currently support these commands, you can use LIO and rbd and it will
still execute them although it would not be offloaded like how you would
want. For example, for write same LIO will just do multiple writes to
the rbd device.
next prev parent reply other threads:[~2015-12-09 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 7:08 RBD Kernel: write_same_max_bytes and SCSI XCOPY Timofey Titovets
2015-12-09 21:37 ` Mike Christie [this message]
2015-12-09 21:44 ` Timofey Titovets
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=56689F07.40502@redhat.com \
--to=mchristi@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=nefelim4ag@gmail.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 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.