From: hch@lst.de (Christoph Hellwig)
Subject: rework NVMe command passthrough
Date: Wed, 9 Nov 2016 20:39:56 +0100 [thread overview]
Message-ID: <20161109193956.GA29228@lst.de> (raw)
In-Reply-To: <1477411779-2993-1-git-send-email-hch@lst.de>
Jens, Keith:
any opinion on this series? I'd really prefer to have something
like this in before merging the NVMe FC support.
On Tue, Oct 25, 2016@06:09:37PM +0200, Christoph Hellwig wrote:
> Hi all,
>
> this series started out as part of my attempt to get rid of the SCSI
> passthrough fields in struct request, but reviewing the NVMe FC patches
> and subsequent discussion with James gave them additional priority.
>
> This series introduce? a nvme nvme_request structure common to all
> transports, which allows us to stop abusing the SCSI passthrough fields
> in struct request, and also allows us to stop passing the full CQE
> up to the callers of the request interface which is rather painful
> for FC.
>
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
---end quoted text---
next prev parent reply other threads:[~2016-11-09 19:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 16:09 rework NVMe command passthrough Christoph Hellwig
2016-10-25 16:09 ` [PATCH 1/2] nvme: introduce struct nvme_request Christoph Hellwig
2016-10-26 18:05 ` James Smart
[not found] ` <2aa1235b-8dae-3399-7d7b-2ebed8ad53c5@broadcom.com>
[not found] ` <98e72062-abb2-e596-cbdd-d6f915f8ba4d@broadcom.com>
2016-10-27 7:16 ` Christoph Hellwig
2016-10-27 9:24 ` Sagi Grimberg
2016-10-27 12:30 ` Christoph Hellwig
2016-10-25 16:09 ` [PATCH 2/2] nvme: don't pass the full CQE to nvme_complete_async_event Christoph Hellwig
2016-10-25 16:53 ` Christoph Hellwig
2016-11-09 19:39 ` Christoph Hellwig [this message]
2016-11-09 20:00 ` rework NVMe command passthrough Keith Busch
2016-11-09 21:45 ` Christoph Hellwig
2016-11-09 20:54 ` Jens Axboe
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=20161109193956.GA29228@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;
as well as URLs for NNTP newsgroup(s).