From: keith.busch@intel.com (Keith Busch)
Subject: NVMe driver status
Date: Tue, 20 Jan 2015 15:46:36 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1501201537470.15481@localhost.lm.intel.com> (raw)
In-Reply-To: <000d01d034a8$fa00f060$ee02d120$@samsung.com>
Okay, I added the repo to here:
http://git.infradead.org/users/kbusch/nvme-legacy.git
It's based off linux-stable v3.18.3, plus a merge from linux-nvme for
nvme parts that were not committed upstream by 3.18.
I don't know what kind of activity to expect this will get, but I'll be
happy to merge applicable upstream commits and apply patches for any new
features or bug fixes people want to see in the bio-based nvme driver.
On Tue, 20 Jan 2015, Sunad Bhandary wrote:
> Hi Keith,
>
> Thanks for clarifying the situation.
>
> If suppose the bio-based driver version is pushed out to a public repo, will
> it be made just a source repo or
> will it be actively maintained where new patches are acceptable and can be
> merged into the repo ?
>
> Thanks and regards,
> Sunad
>
> -----Original Message-----
> From: Linux-nvme [mailto:linux-nvme-bounces at lists.infradead.org] On Behalf
> Of Keith Busch
> Sent: Monday, January 19, 2015 8:03 PM
> To: Sunad Bhandary
> Cc: 'Keith Busch'; linux-nvme at lists.infradead.org
> Subject: Re: NVMe driver status
>
> Hi Sunad,
>
> The mainline going forward with kernel 3.19 will be blk-mq, and the
> linux-nvme tree will be there as well on the next upstream merge.
>
> I have my own repo for maintaining the bio-based version since a lot of OS
> vendors are using older kernels in their minor release cycles. I can push
> this out to a public repo on git.infradead.org if there's interest.
>
> Thanks,
> Keith
>
> On Mon, 19 Jan 2015, Sunad Bhandary wrote:
>> Hi Keith,
>>
>> Currently there are two different variants of the NVMe driver, one
>> with the multi-queue implementation which is under active development
>> and the one without it which is the current driver hosted in the NVMe git
> page.
>>
>> Going forward will the non-multi queue driver also be maintained or
>> will it be done away with completely ?
>>
>> Regards,
>> Sunad
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2015-01-20 15:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 12:00 NVMe driver status Sunad Bhandary
2015-01-19 14:33 ` Keith Busch
2015-01-20 12:02 ` Sunad Bhandary
2015-01-20 15:46 ` Keith Busch [this message]
2015-03-10 15:20 ` Sunad Bhandary
2015-03-10 19:11 ` David Darrington
2015-03-10 20:01 ` Keith Busch
2015-03-11 18:06 ` Brandon Schulz
2015-03-11 18:40 ` Keith Busch
2015-03-11 21:17 ` Brandon Schulz
2015-03-12 2:01 ` Keith Busch
2015-03-12 16:32 ` Brandon Schulz
2015-03-16 14:52 ` Brandon Schulz
2015-03-16 17:19 ` Keith Busch
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=alpine.LNX.2.00.1501201537470.15481@localhost.lm.intel.com \
--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