From: Artem Bityutskiy <dedekind1@gmail.com>
To: David Brownell <david-b@pacbell.net>
Cc: Andrew McKay <amckay@iders.ca>,
linux-mtd@lists.infradead.org, JiSheng Zhang <jszhang3@gmail.com>
Subject: Re: nand_update_bbt fix
Date: Thu, 13 Aug 2009 08:48:06 +0300 [thread overview]
Message-ID: <1250142486.25202.17.camel@localhost> (raw)
In-Reply-To: <200908121037.55941.david-b@pacbell.net>
On Wed, 2009-08-12 at 10:37 -0700, David Brownell wrote:
> On Tuesday 11 August 2009, Artem Bityutskiy wrote:
> > My position is:
> > * vmalloc is a problem because it prevents DMA
> > * kmalloc is a problem because large allocations of contiguous memory
> > are impossible
> >
> > Thus, I think people should invent some nice solution for the whole issue
> > instead of turning vmalloc's into kmallocks and back and forth.
>
> BBT is a constrained sub-problem, but not the only one.
>
> (Another BBT issue: I've thought that with MLC chips and their
> small limits on number-of-erases, the current waste of BBT pages
> deserves more attention. On a 2 GByte chip with 4KB pages and
> blocks at 256KB, each block could hold 64 BBT versions, with
> newer ones after older ones, even at one-per-page. But today's
> BBT code is dumb: one-per-block. That's a lot of needless and
> extra erasures for BBT blocks...)
Agree. IMO, today's MTD is fits the "ancient crap" classification, and
badly needs some brave knight who would improve it.
> > I'm CCing
> > David Brownell because AFAIR he was discussing similar things on lkml some
> > time ago.
>
> The MTD stack is DMA-unfriendly today.
>
> The issue I saw was with SPI flash chips, where the underlying
> SPI master controller often uses DMA ... causing trouble for
> certain code paths through MTD (or was it just JFFS2?).
UBI / UBIFS also send vmalloc'ed buffers :-)
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2009-08-13 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 23:04 nand_update_bbt fix Andrew McKay
2009-08-11 15:39 ` Artem Bityutskiy
2009-08-11 16:03 ` Andrew McKay
2009-08-12 5:51 ` Artem Bityutskiy
2009-08-12 17:37 ` David Brownell
2009-08-13 5:48 ` Artem Bityutskiy [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=1250142486.25202.17.camel@localhost \
--to=dedekind1@gmail.com \
--cc=amckay@iders.ca \
--cc=david-b@pacbell.net \
--cc=jszhang3@gmail.com \
--cc=linux-mtd@lists.infradead.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.