From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Mike Frysinger <vapier@gentoo.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
Richard Weinberger <richard@nod.at>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Michael Opdenacker <michael.opdenacker@free-electrons.com>,
Piergiorgio Beruto <piergiorgio.beruto@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 1/1] ubi: Introduce block devices for UBI volumes
Date: Sun, 9 Feb 2014 23:48:28 -0300 [thread overview]
Message-ID: <20140210024827.GB9643@localhost> (raw)
In-Reply-To: <20140209075157.GJ22376@1wt.eu>
On Sun, Feb 09, 2014 at 08:51:57AM +0100, Willy Tarreau wrote:
[..]
>
> > > This I think it's a bad idea to artificially remove some features
> > > if they're not broken.
> >
> > Your arguments have convinced me, let's keep it and hope the best.
>
Let me add that keeping the write support follows the whole "mechanism,
not policy" kernel motto, doesn't it?
Regarding users, well the option looks like this:
[ ] Enable write support (DANGEROUS)
I think any user would think twice before enabling it.
Regaring the maintainability: the implementation is *really* simple,
and won't add much complexity.
Let's not prevent someone from divising a wear level aware block filesystem
and using it on top of ubiblock. And perhaps f2fs already does a good job!
Keeping this support would allow someone to take the lead and get some real
numbers on that.
As I said, the implementation is so simple that it seems a pity to just
drop it.
BTW, v5 (this is v4 which I forgot to add to the subject) is already on the
oven, with the fixes pointed out by Richard.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-10 2:48 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 20:38 [PATCH 0/1] ubi: Introduce block devices for UBI volumes Ezequiel Garcia
2014-01-29 20:38 ` [PATCH 1/1] " Ezequiel Garcia
2014-01-31 17:06 ` Willy Tarreau
2014-02-04 11:06 ` Ezequiel Garcia
2014-02-08 16:50 ` Ezequiel Garcia
2014-02-08 21:37 ` Richard Weinberger
2014-02-08 22:51 ` Willy Tarreau
2014-02-08 22:56 ` Richard Weinberger
2014-02-08 23:01 ` Willy Tarreau
2014-02-08 23:10 ` Piergiorgio Beruto
2014-02-08 23:13 ` Richard Weinberger
2014-02-08 23:15 ` Willy Tarreau
2014-02-08 23:25 ` Richard Weinberger
2014-02-08 23:37 ` Willy Tarreau
2014-02-09 0:17 ` Richard Weinberger
2014-02-09 7:51 ` Willy Tarreau
2014-02-10 2:48 ` Ezequiel Garcia [this message]
2014-02-10 7:35 ` Artem Bityutskiy
2014-02-10 8:27 ` Ezequiel Garcia
2014-02-10 8:46 ` Willy Tarreau
2014-02-10 14:20 ` Ezequiel Garcia
2014-02-10 14:41 ` Richard Weinberger
2014-02-10 14:50 ` Artem Bityutskiy
2014-02-10 14:52 ` Bityutskiy, Artem
2014-02-10 16:15 ` Willy Tarreau
2014-02-10 14:53 ` Bityutskiy, Artem
2014-02-10 18:48 ` Ezequiel Garcia
[not found] ` <a86d653a-9e3b-46dc-9ec8-94a9c1099bec@email.android.com>
2014-02-10 21:43 ` Willy Tarreau
2014-02-11 8:37 ` Geert Uytterhoeven
2014-02-11 9:05 ` Willy Tarreau
2014-02-11 9:35 ` Ezequiel Garcia
2014-02-11 9:43 ` Peter Korsgaard
2014-02-11 10:21 ` Geert Uytterhoeven
2014-02-10 22:37 ` Thomas Petazzoni
[not found] ` <de976336-3144-4f21-859b-d1a37fc3d811@email.android.com>
2014-02-10 22:46 ` Thomas Petazzoni
[not found] ` <a3fc06a8-c809-4687-9da4-015bd8dd29e8@email.android.com>
2014-02-10 23:01 ` Thomas Petazzoni
2014-02-10 23:19 ` Ezequiel Garcia
2014-02-10 8:50 ` Artem Bityutskiy
2014-02-08 23:05 ` Piergiorgio Beruto
2014-02-08 23:13 ` Willy Tarreau
2014-02-10 8:42 ` Thomas Petazzoni
2014-02-10 8:51 ` Willy Tarreau
2014-02-10 1:29 ` Ezequiel Garcia
2014-02-10 7:53 ` Richard Weinberger
2014-02-10 8:12 ` Ezequiel Garcia
2014-02-10 8:24 ` Artem Bityutskiy
2014-02-10 8:37 ` Willy Tarreau
2014-02-10 8:50 ` Ezequiel Garcia
2014-02-09 22:56 ` Richard Weinberger
2014-02-10 2:36 ` Ezequiel Garcia
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=20140210024827.GB9643@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael.opdenacker@free-electrons.com \
--cc=piergiorgio.beruto@gmail.com \
--cc=richard@nod.at \
--cc=thomas.petazzoni@free-electrons.com \
--cc=vapier@gentoo.org \
--cc=w@1wt.eu \
/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.