From: james.smart@broadcom.com (James Smart)
Subject: [PATCH 0/3] nvme-fabrics: Add NVME FC Transport support to lpfc
Date: Mon, 22 Aug 2016 10:41:51 -0700 [thread overview]
Message-ID: <a6ea99aa-a405-6438-627f-e7c904d0ac0a@broadcom.com> (raw)
In-Reply-To: <20160811212406.GI18013@infradead.org>
On 8/11/2016 2:24 PM, Christoph Hellwig wrote:
> On Fri, Jul 22, 2016@05:24:00PM -0700, James Smart wrote:
>> This patchset adds NVME support to the lpfc FC driver. It reworks
>> the core driver for both NVME and SCSI protocol support, then adds the
>> nvme-over-fabrics host and target interfaces which connect to the
>> NVME FC transport lower-level api.
>>
>> Patches are cut against the linux-nvme for-4.8/drivers branch
> Before reviewing the details: what's the plan for merging this as we'll
> have dependencies on both the SCSI and the block tree?
Good question. With the first round of lpfc patches, I tried to ensure
we had all the cross-protocol infrastructure in place such that the
driver can have 2 halves that effectively run independently. I'm hoping
it means that I can submit scsi stuff independent from nvme stuff, but
we'll have to see how it goes over time.
I'm open to suggestions on how best to manage the 2 trees - e.g. scsi
stuff goes in scsi tree, and if a dependency then has to be pulled into
block ? nvme stuff only to block. The initial lpfc patch set should
have all the scsi infrastructure pulled into the 4.8 merge, so hopefully
that dependency has been resolved already.
-- james
Any recommendations ?
WARNING: multiple messages have this Message-ID (diff)
From: James Smart <james.smart@broadcom.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/3] nvme-fabrics: Add NVME FC Transport support to lpfc
Date: Mon, 22 Aug 2016 10:41:51 -0700 [thread overview]
Message-ID: <a6ea99aa-a405-6438-627f-e7c904d0ac0a@broadcom.com> (raw)
In-Reply-To: <20160811212406.GI18013@infradead.org>
On 8/11/2016 2:24 PM, Christoph Hellwig wrote:
> On Fri, Jul 22, 2016 at 05:24:00PM -0700, James Smart wrote:
>> This patchset adds NVME support to the lpfc FC driver. It reworks
>> the core driver for both NVME and SCSI protocol support, then adds the
>> nvme-over-fabrics host and target interfaces which connect to the
>> NVME FC transport lower-level api.
>>
>> Patches are cut against the linux-nvme for-4.8/drivers branch
> Before reviewing the details: what's the plan for merging this as we'll
> have dependencies on both the SCSI and the block tree?
Good question. With the first round of lpfc patches, I tried to ensure
we had all the cross-protocol infrastructure in place such that the
driver can have 2 halves that effectively run independently. I'm hoping
it means that I can submit scsi stuff independent from nvme stuff, but
we'll have to see how it goes over time.
I'm open to suggestions on how best to manage the 2 trees - e.g. scsi
stuff goes in scsi tree, and if a dependency then has to be pulled into
block ? nvme stuff only to block. The initial lpfc patch set should
have all the scsi infrastructure pulled into the 4.8 merge, so hopefully
that dependency has been resolved already.
-- james
Any recommendations ?
next prev parent reply other threads:[~2016-08-22 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 0:24 [PATCH 0/3] nvme-fabrics: Add NVME FC Transport support to lpfc James Smart
2016-07-23 0:24 ` James Smart
2016-08-11 21:24 ` Christoph Hellwig
2016-08-11 21:24 ` Christoph Hellwig
2016-08-22 17:41 ` James Smart [this message]
2016-08-22 17:41 ` James Smart
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=a6ea99aa-a405-6438-627f-e7c904d0ac0a@broadcom.com \
--to=james.smart@broadcom.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 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.