From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Richard Weinberger <richard@nod.at>
Cc: Benson Young <benson6877@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
David Gstir <david@sigma-star.at>, Willy Tarreau <w@1wt.eu>
Subject: Re: ubiblock RW
Date: Fri, 25 Mar 2016 13:51:37 +0200 [thread overview]
Message-ID: <1458906697.615.20.camel@gmail.com> (raw)
In-Reply-To: <CAAEAJfDXB34SWoCMXBiqEFSRMWAxZpGmMR9tPdsN=mokO8fkhw@mail.gmail.com>
On Thu, 2016-03-24 at 18:26 -0300, Ezequiel Garcia wrote:
> > > Richard, what do you think?
> > I'm definitely not fond of adding write support to ubiblock without
> > turning it into a proper FTL.
> > Otherwise it will be abused and will cause serious damage.
> >
> I'm not sure this statement makes much sense without actual numbers.
Ezequel,
could you re-summarize how the write support would be implemented? Read
entire LEB, modify data block (512 bytes), atomically write the LEB?
This would not perform well, but would probably work.
Or you want to avoid atomic LEB change and just erase the LEB and write
the entire LEB with the updated contents? This would probably be a bit
faster, but not power-cut safe.
next prev parent reply other threads:[~2016-03-25 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABJ+KKu2RJuHXE3LpmzSYtE0i57sHDUHWOxPxufCP94RTa=eBA@mail.gmail.com>
2016-03-24 14:23 ` ubiblock RW Ezequiel Garcia
2016-03-24 20:38 ` Richard Weinberger
2016-03-24 21:26 ` Ezequiel Garcia
2016-03-24 21:39 ` Willy Tarreau
2016-03-25 20:28 ` Richard Weinberger
2016-03-25 11:51 ` Artem Bityutskiy [this message]
2016-03-25 20:50 ` Ezequiel Garcia
2016-03-25 20:51 ` Ezequiel Garcia
2016-03-25 21:25 ` Richard Weinberger
2016-03-26 6:01 ` Willy Tarreau
2016-03-27 22:01 ` Richard Weinberger
2016-03-28 6:56 ` Artem Bityutskiy
2016-03-28 8:17 ` Willy Tarreau
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=1458906697.615.20.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=benson6877@gmail.com \
--cc=david@sigma-star.at \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox