From: David Brownell <david-b@pacbell.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kyungmin Park <kmpark@infradead.org>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Michael Trimarchi <trimarchimichael@yahoo.it>,
spi-devel-general@lists.sourceforge.net,
Josh Boyer <jwboyer@gmail.com>,
dwmw2@infradead.org, linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] jffs2 summary allocation
Date: Fri, 4 Apr 2008 19:41:34 -0700 [thread overview]
Message-ID: <200804041941.35075.david-b@pacbell.net> (raw)
In-Reply-To: <20080404184615.deaf3122.akpm@linux-foundation.org>
On Friday 04 April 2008, Andrew Morton wrote:
> This problem comes up pretty often.
Which problem -- kmalloc(BIG)? Or dma(dma-unsafe-mem)?
Or something else?
The specific issue here might best be described as JFFS2
making a bad assumption: that MTD drivers never use DMA.
The I2C stack does that in some cases (for example, I/O
buffers in i2c_smbus_xfer_emulated are on-stack), but I'd
not call that an especially common assumption.
> Rather than open-coding it yet again
> it'd be nice to have a little bit of library code which manages an array of
> pages and which has accessors for common operations like
> read/write-u8/u16/u32/u64, memset, memcpy, etc.
If array-of-pages is to be more widely adopted, that'd
make sense. The MTD framework is a bit odd in that
respect ... it has block devices but doesn't use the
scatterlist primitives.
- Dave
next prev parent reply other threads:[~2008-04-05 2:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 10:23 [PATCH] jffs2 summary allocation Michael Trimarchi
2008-04-04 19:48 ` Andrew Morton
2008-04-04 20:09 ` Russell King - ARM Linux
2008-04-04 23:09 ` David Brownell
2008-04-04 23:21 ` Josh Boyer
2008-04-04 23:58 ` David Brownell
2008-04-05 1:11 ` Josh Boyer
2008-04-05 1:29 ` Kyungmin Park
2008-04-05 1:46 ` Andrew Morton
2008-04-05 2:41 ` David Brownell [this message]
2008-04-05 3:27 ` Andrew Morton
2008-04-05 2:17 ` David Brownell
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=200804041941.35075.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=jwboyer@gmail.com \
--cc=kmpark@infradead.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=trimarchimichael@yahoo.it \
/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