From: David Brownell <david-b@pacbell.net>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: Nicolas Ferre <nicolas.ferre@rfo.atmel.com>,
linux-mtd@lists.infradead.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.6.26-rc5-git] at91_nand speedup via {read, write}s{b, w}()
Date: Mon, 9 Jun 2008 11:21:53 -0700 [thread overview]
Message-ID: <200806091121.53579.david-b@pacbell.net> (raw)
In-Reply-To: <20080609194859.3a9b5fcb@hskinnemo-gx745.norway.atmel.com>
On Monday 09 June 2008, Haavard Skinnemoen wrote:
> > real 0m20.226s
> > user 0m0.010s
> > sys 0m6.000s
>
> Hmm, that's odd. What's the CPU doing during the remaining 14 seconds?
> It can't possibly be sleeping?
>
> Ah, it's I/O wait, isn't it? Because you're going through the block
> layer?
Some of it is surely data copying, but yes /dev/mtdblock0 might
have something to do with it. I was puzzled by this too, which
is part of why I quoted only elapsed time.
> Yeah...I'm still not sure where to send it though, since it touches
> three different subsystems. I can set up a separate tree for it like
> I've done a couple of times before...though I'm not sure if anyone ever
> pulls it.
Three subsystems ... you mean, ARM, AVR32, MTD? If MTD patches
merged more promptly, I'd suggest it goes through there. Else
maybe you should just get acks from the other maintainers and
push the rename+ directly to Linus once 2.6.27-rc0 starts.
- Dave
prev parent reply other threads:[~2008-06-09 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 10:13 [patch 2.6.26-rc5-git] at91_nand speedup via {read,write}s{b,w}() David Brownell
2008-06-09 11:31 ` Haavard Skinnemoen
2008-06-09 16:49 ` Haavard Skinnemoen
2008-06-09 17:07 ` [patch 2.6.26-rc5-git] at91_nand speedup via {read, write}s{b, w}() David Brownell
2008-06-09 17:48 ` [patch 2.6.26-rc5-git] at91_nand speedup via {read,write}s{b,w}() Haavard Skinnemoen
2008-06-09 18:21 ` David Brownell [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=200806091121.53579.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=haavard.skinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nicolas.ferre@rfo.atmel.com \
/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