From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCHv3] NVMe: Spliting large i/o in the ioctl path
Date: Mon, 27 Apr 2015 12:27:07 -0700 [thread overview]
Message-ID: <20150427192707.GA32438@infradead.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1504271915450.19844@localhost.lm.intel.com>
On Mon, Apr 27, 2015@07:22:29PM +0000, Keith Busch wrote:
> On Mon, 27 Apr 2015, sathyavathi wrote:
> >Keith,
> >
> >Any update on this patch.
>
> No new comments your implementation. This ioctl is not a critical or
> fast path though, so I'm not sure why we'd force the kernel driver to
> correct a malformed passthru.
>
> Basically, I'm on the side that if your app misuses the ioctl, you get
> to keep both pieces. Your patch is available if a maintainer disagrees.
Btw, I'll send a patch soon will make the ioctl and SCSI code use the block
layer S/G mapping, which will give us this feature for free. It might make
sense to hold out for it. I'll prioritize finishing this one so I can
get it out ASAP.
next prev parent reply other threads:[~2015-04-27 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D.9F.25582.055AF255@epcpsbge3.samsung.com>
2015-04-27 11:26 ` [PATCHv3] NVMe: Spliting large i/o in the ioctl path sathyavathi
2015-04-27 19:22 ` Keith Busch
2015-04-27 19:27 ` Christoph Hellwig [this message]
2015-04-02 6:06 Sathyavathi M
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=20150427192707.GA32438@infradead.org \
--to=hch@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox