From: Hitoshi Mitake <mitake.hitoshi@gmail.com>
To: Ronnie Sahlberg <ronniesahlberg@gmail.com>
Cc: stgt@vger.kernel.org
Subject: Re: [PATCH] Add an array that describes which opcodes are supported by the RDWR and SHEEPDOG backends.
Date: Thu, 17 Oct 2013 22:47:00 +0900 [thread overview]
Message-ID: <87vc0wqaaz.wl%mitake.hitoshi@gmail.com> (raw)
In-Reply-To: <1381588740-25968-2-git-send-email-ronniesahlberg@gmail.com>
Hi Ronnie,
At Sat, 12 Oct 2013 07:38:59 -0700,
Ronnie Sahlberg wrote:
>
> While RDWR supports all SBC opcodes that TGTD implement SHEEPDOG
> only supports a subset and lacks the following opcodes:
> WRITE_VERIFY10/12/16 VERIFY10/12/16 PREFETCH10/16
> WRITE_SAME10/16 UNMAP and ORWRITE
>
> This allows backends to specify which opcodes it is prepared to process
> and which commands should fail with invalid op code
> and allows SHEEPDOG backed LUNs to respond with INVALID_OP_CODE
> correctly.
>
> This is most useful for block devices where we have several different backens
> and where some backends only support a subset of the commands
>
> Signed-off-by: Ronnie Sahlberg <ronniesahlberg@gmail.com>
> ---
> usr/bs.c | 8 ++++++++
> usr/bs_rdwr.c | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
> usr/bs_sheepdog.c | 38 ++++++++++++++++++++++++++++++++++++++
> usr/scsi.c | 6 ++++++
> usr/tgtd.h | 1 +
> 5 files changed, 104 insertions(+), 0 deletions(-)
>
Thanks a lot for the change! This patch looks good to me. I'll try to
implement these missing opcode in bs_sheepdog.c, but it will take time
and your solution is a great help.
Thanks,
Hitoshi
next prev parent reply other threads:[~2013-10-17 13:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1381588740-25968-1-git-send-email-ronniesahlberg@gmail.com>
[not found] ` <1381588740-25968-2-git-send-email-ronniesahlberg@gmail.com>
2013-10-16 16:05 ` [PATCH] Add an array that describes which opcodes are supported by the RDWR and SHEEPDOG backends ronnie sahlberg
2013-10-17 13:47 ` Hitoshi Mitake [this message]
2013-10-20 13:38 ` ronnie sahlberg
2013-10-21 1:34 ` FUJITA Tomonori
2013-10-31 1:44 ` ronnie sahlberg
2013-11-05 14:39 ` ronnie sahlberg
2013-11-07 7:07 ` FUJITA Tomonori
2013-11-07 16:42 ` ronnie sahlberg
2013-11-07 21:39 ` FUJITA Tomonori
2013-11-07 21:46 ` Dan Mick
2013-11-07 21:51 ` FUJITA Tomonori
2013-11-07 22:15 ` Dan Mick
2013-11-17 1:18 [PATCH] Add an array that describes which opcodes are supported by backends Ronnie Sahlberg
2013-11-17 1:18 ` [PATCH] Add an array that describes which opcodes are supported by the RDWR and SHEEPDOG backends Ronnie Sahlberg
2013-11-17 13:23 ` FUJITA Tomonori
2013-11-24 16:39 ` ronnie sahlberg
2013-11-24 21:06 ` FUJITA Tomonori
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=87vc0wqaaz.wl%mitake.hitoshi@gmail.com \
--to=mitake.hitoshi@gmail.com \
--cc=ronniesahlberg@gmail.com \
--cc=stgt@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 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.