From: keith.busch@intel.com (Keith Busch)
Subject: 2016 Changes to nvme.h
Date: Thu, 24 Jan 2019 15:21:27 -0700 [thread overview]
Message-ID: <20190124222127.GA9925@localhost.localdomain> (raw)
In-Reply-To: <75a8b8ac-fa85-39c8-0da6-cc7629422d00@panasas.com>
On Thu, Jan 24, 2019@09:38:11PM +0000, Wilson, Ellis wrote:
> Thank you for the response. I think I understand the intent now. Your
> comment about a userspace library makes total sense. I still disagree
> with one thing. You say, "it is just not a good idea to rely on the
> kernel to own updating the structures when the kernel has no internal
> need for it." And yet, those very structures were moved further
> /inside/, rather than being deleted wholesale, so the action doesn't
> quite match up with your explanation from what I can tell.
We do have in-kernel uses for nvme structures, hence the relocation to
an internal definition. We just don't want to export it for user space,
which would (and did) create undue maintenance to non-kernel usage.
prev parent reply other threads:[~2019-01-24 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 16:59 2016 Changes to nvme.h Wilson, Ellis
2019-01-24 17:21 ` Keith Busch
2019-01-24 21:38 ` Wilson, Ellis
2019-01-24 22:21 ` Keith Busch [this message]
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=20190124222127.GA9925@localhost.localdomain \
--to=keith.busch@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox