From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH RFC] nvmet: emulate noiob boundary
Date: Mon, 22 Oct 2018 10:59:12 +0200 [thread overview]
Message-ID: <20181022085912.GE18755@lst.de> (raw)
In-Reply-To: <20181019222437.25289-1-sagi@grimberg.me>
On Fri, Oct 19, 2018@03:24:37PM -0700, Sagi Grimberg wrote:
> Useful to exercise the host driver to noiob support without having device
> that actually require it.
This code looks ok to me, but I'm rather worried about adding these
just for fun features - we'll eventually have a configfs mess just
like the scsi target code if we just keep adding random options.
next prev parent reply other threads:[~2018-10-22 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 22:24 [PATCH RFC] nvmet: emulate noiob boundary Sagi Grimberg
2018-10-22 8:59 ` Christoph Hellwig [this message]
2018-10-23 0:29 ` Sagi Grimberg
2018-10-23 6:50 ` Chaitanya Kulkarni
2018-10-23 7:31 ` Sagi Grimberg
2018-10-26 7:54 ` Christoph Hellwig
2018-10-30 18:33 ` Sagi Grimberg
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=20181022085912.GE18755@lst.de \
--to=hch@lst.de \
/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