All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matias Bjorling <m@bjorling.me>
To: device-mapper development <dm-devel@redhat.com>,
	snitzer@redhat.com, agk@redhat.com, neilb@suse.de,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [dm-devel] [PATCH RFC v1 00/01] dm-lightnvm introduction
Date: Fri, 21 Mar 2014 08:22:24 -0700	[thread overview]
Message-ID: <532C5930.7040107@bjorling.me> (raw)
In-Reply-To: <20140321090630.GA30044@debian>

On 03/21/2014 02:06 AM, Joe Thornber wrote:
> Hi Matias,
> 
> This looks really interesting and I'd love to get involved.  Do you
> have any recommendations for what hardware I should pick up?

Hi Joe,

The most easily available platform is OpenSSD
(http://www.openssd-project.org). It's a little old, but still very
functional. When there's a good firmware implementation, I think it will
be easier for the custom SSD vendor's to jump on board with their own
firmware.

- Matias

> 
> - Joe
> 
> 
> On Thu, Mar 20, 2014 at 11:32:17PM -0700, Matias Bjørling wrote:
>> Hi,
>>
>> Users that have custom firmware SSDs, may choose to expose their flash directly.
>> This allows the host to control logical to physical address mappings, garbage
>> collection strategy, wear-leveling, and so on.

  reply	other threads:[~2014-03-21 15:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21  6:32 [PATCH RFC v1 00/01] dm-lightnvm introduction Matias Bjørling
2014-03-21  6:32 ` Matias Bjørling
2014-03-21  6:32 ` [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for open firmware SSDs Matias Bjørling
2014-03-21 15:09   ` Mike Snitzer
2014-03-21 15:09     ` Mike Snitzer
2014-03-21 15:26     ` Matias Bjorling
2014-03-21 15:26       ` Matias Bjorling
2014-03-21 15:37   ` Christoph Hellwig
2014-03-21 16:24     ` Matias Bjorling
2014-03-25  2:22       ` [dm-devel] " Akira Hayakawa
2014-03-25  3:45         ` Matias Bjorling
2014-03-24  6:13     ` Bart Van Assche
2014-03-25  3:30       ` Matias Bjorling
2014-03-25 11:38         ` Takashi HOSHINO
2014-03-25 11:38           ` [dm-devel] " Takashi HOSHINO
2014-03-21  9:06 ` [dm-devel] [PATCH RFC v1 00/01] dm-lightnvm introduction Joe Thornber
2014-03-21 15:22   ` Matias Bjorling [this message]
2014-03-25  3:08     ` David Lang
2014-03-25  3:56       ` Matias Bjorling
2014-03-25  3:56         ` Matias Bjorling
2014-03-25 17:23         ` Richard Weinberger
2014-03-21 15:32 ` Richard Weinberger
2014-03-21 15:32   ` Richard Weinberger
2014-03-21 16:42   ` Matias Bjorling

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=532C5930.7040107@bjorling.me \
    --to=m@bjorling.me \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=snitzer@redhat.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.