From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Mike Frysinger <vapier@gentoo.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
Michael Opdenacker <michael.opdenacker@free-electrons.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Tim Bird <tim.bird@am.sony.com>,
Piergiorgio Beruto <piergiorgio.beruto@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>, Willy Tarreau <w@1wt.eu>
Subject: Re: [PATCH 1/1] ubi: Introduce block devices for UBI volumes
Date: Sun, 9 Feb 2014 23:36:35 -0300 [thread overview]
Message-ID: <20140210023634.GA9643@localhost> (raw)
In-Reply-To: <CAFLxGvyzWhMHjxM=0kgsEOx82qAGBWE1WbyLJt2-6P7Cd9i+nQ@mail.gmail.com>
On Sun, Feb 09, 2014 at 11:56:24PM +0100, Richard Weinberger wrote:
> On Wed, Jan 29, 2014 at 9:38 PM, Ezequiel Garcia
> <ezequiel.garcia@free-electrons.com> wrote:
[..]
> > +
> > +static int ubiblock_read_to_buf(struct ubiblock *dev, char *buffer,
> > + int leb, int offset, int len)
> > +{
> > + int ret;
> > + char *cache_buffer;
> > + /*
> > + * First try in cache, if it's not there load this leb.
> > + * Note that reading never flushes to disk!
> > + */
> > + if (leb_in_cache(&dev->cache, leb)) {
> > + cache_buffer = dev->cache.buffer;
> > + } else {
>
> I think you have to flush the cache here too.
> With RW support enabled you can end up with a dirty cache here.
>
Yes, right. This is a left-over from the two-cache design. Now that we
have just one cache, it's possible to flush it before filling it.
Good catch!
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
prev parent reply other threads:[~2014-02-10 2:37 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
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 [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=20140210023634.GA9643@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.weinberger@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tim.bird@am.sony.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).