public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matias <mb@lightnvm.io>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH v6 0/5] Support for Open-Channel SSDs
Date: Tue, 04 Aug 2015 13:58:32 +0200	[thread overview]
Message-ID: <55C0A8E8.7040308@lightnvm.io> (raw)
In-Reply-To: <20150804113013.GC8395@infradead.org>

On 08/04/2015 01:30 PM, Christoph Hellwig wrote:
> Hi Matias,
>
> the architecture looks fine to me.  Probab;y not worth merging until
> your have the multipage I/O sorted out and real hardware, or do you want
> to aim for fast inclusion?
>

Hi Christoph,

The multipage will come in v7. Javier has it flushed out, and we are 
just going through the last nitpicks on it.

I'll like to get it included. There is some out-of-tree work that is 
based on it, which requires that the kernel and the modules are compiled 
together. Having the core part in the kernel will be very helpful.

(resending to the lists. Forgot to put gmail in plain text mode)

      reply	other threads:[~2015-08-04 11:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 11:17 [PATCH v6 0/5] Support for Open-Channel SSDs Matias Bjørling
2015-07-28 11:17 ` [PATCH v6 1/5] lightnvm: " Matias Bjørling
2015-07-28 11:17 ` [PATCH v6 2/5] lightnvm: Hybrid Open-Channel SSD RRPC target Matias Bjørling
2015-07-28 11:17 ` [PATCH v6 3/5] lightnvm: Hybrid Open-Channel SSD block manager Matias Bjørling
2015-07-28 11:17 ` [PATCH v6 4/5] null_nvm: Lightnvm test driver Matias Bjørling
2015-07-28 11:17 ` [PATCH v6 5/5] nvme: LightNVM support Matias Bjørling
2015-08-02  7:57   ` Pavel Machek
2015-08-04 12:00     ` Matias
2015-08-04 11:30 ` [PATCH v6 0/5] Support for Open-Channel SSDs Christoph Hellwig
2015-08-04 11:58   ` Matias [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=55C0A8E8.7040308@lightnvm.io \
    --to=mb@lightnvm.io \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.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