From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH RFC] nvmet: emulate noiob boundary
Date: Fri, 26 Oct 2018 09:54:28 +0200 [thread overview]
Message-ID: <20181026075428.GD5092@lst.de> (raw)
In-Reply-To: <1fc9b542-caa0-4696-d2bd-5722b97a17c8@grimberg.me>
On Mon, Oct 22, 2018@05:29:55PM -0700, Sagi Grimberg wrote:
> Well, this helped me debug a sub-page bio split code path that I
> wouldn't be able to generate without, so I think its beneficial
> to have a knob for it.
>
> In general, I would be in favor of us having the kernel target
> allow one to exercise the host code in various forms, but would not
> want to have endless attributes to setup. Perhaps we would want to have
> these sort of stuff with a debug prefix such that its clear that only
> debug stuff belong there?
Yes, maybe we could have a config option to turn on this pure debug
code. For noiob in particular it might make sense to just pass
it up if the lower level device has it, though.
next prev parent reply other threads:[~2018-10-26 7:54 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
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 [this message]
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=20181026075428.GD5092@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 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.