From: Artem Bityutskiy <dedekind1@gmail.com>
To: Kent Overstreet <koverstreet@google.com>
Cc: "Loke, Chetan" <Chetan.Loke@netscout.com>,
lsf-pc@lists.linux-foundation.org, linux-scsi@vger.kernel.org,
linux-fsdevel@vger.kernel.org, dedekind@infradead.org
Subject: Re: [ATTEND]
Date: Thu, 09 Feb 2012 08:34:12 +0200 [thread overview]
Message-ID: <1328769265.2112.0.camel@koala> (raw)
In-Reply-To: <CAH+dOxLxL7CzMk+sLcAUO==4ShtS4JHfgaGRSMmP49LXWVC+fw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
On Wed, 2012-02-08 at 12:48 -0800, Kent Overstreet wrote:
> On Wed, Feb 8, 2012 at 12:20 PM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > Hi, UBI is not an FTL, but it implements a lot of things a decent FTL
> > would also need to implement. And implementing FTL on top of UBI would
> > be much simpler than on top of a raw flash (I assume you are discussing
> > a flash?). UBI has it's own strong sides and limitations. Here I
> > described a simple FTL on top of UBI (long time ago):
>
> You going to be at LSF? Would love to talk to other people with
> experience with the gory details of flash :)
Unfortunately no :-(
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2012-02-09 6:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 9:03 [ATTEND] Kent Overstreet
2012-02-02 10:16 ` [ATTEND] Hannes Reinecke
2012-02-02 21:48 ` [ATTEND] Kent Overstreet
2012-02-07 23:31 ` [ATTEND] Loke, Chetan
2012-02-07 23:31 ` [ATTEND] Loke, Chetan
2012-02-08 3:45 ` [ATTEND] Kent Overstreet
2012-02-08 18:15 ` [ATTEND] Loke, Chetan
2012-02-08 18:15 ` [ATTEND] Loke, Chetan
2012-02-08 20:20 ` [ATTEND] Artem Bityutskiy
2012-02-08 20:48 ` [ATTEND] Kent Overstreet
2012-02-09 6:34 ` Artem Bityutskiy [this message]
2012-02-08 20:46 ` [ATTEND] Kent Overstreet
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=1328769265.2112.0.camel@koala \
--to=dedekind1@gmail.com \
--cc=Chetan.Loke@netscout.com \
--cc=dedekind@infradead.org \
--cc=koverstreet@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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 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.