From: David Woodhouse <dwmw2@infradead.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Stefani Seibold <stefani@seibold.net>,
linux-mtd@lists.infradead.org,
Andrew Morton <akpm@linux-foundation.org>,
"Kreuzer, Michael \(NSN - DE/Ulm\)" <michael.kreuzer@nsn.com>
Subject: Re: [Patch] fix MTD CFI/LPDDR flash driver huge latency bug
Date: Fri, 19 Mar 2010 08:29:15 +0000 [thread overview]
Message-ID: <1268987355.4028.33.camel@macbook.infradead.org> (raw)
In-Reply-To: <20100315142421.GB15133@shareable.org>
On Mon, 2010-03-15 at 14:24 +0000, Jamie Lokier wrote:
> > > > The problem is the memcpy operation which is very slow. A cond_resched
> > > > wouldn't help, since the cpu bus is blocked during the transfer of the
> > > > word.
> > >
> > > I mean split the memcpy into multiple smaller memcpys, so that the
> > > total time in each memcpy is limited to something reasonable.
> > >
> > > The check in cond_resched() is fast, especially once cached. memcpy
> > > speed depends a lot on the attached flash and how everything's
> > > configured, varying from 2.5MB/s up to hundreds of MB/s. So how about
> > > doing cond_resched() every 256 bytes?
> > >
> > > -- Jamie
> >
> > I thoght about this aporoach and i don't like this idea. Why not using a
> > preemptible kernel?
>
> Because it introduces too many risks to enable CONFIG_PREEMPT in a
> stable rolled out device which isn't using it already. Especially on
> devices where it's not well tested by other people, and with drivers
> that nobody ever used with CONFIG_PREEMPT before.
>
> And because CONFIG_PREEMPT isn't always better. (Why do you think
> it's a config option?)
>
> As a bug fix for observed high scheduling latency when a flash I/O is
> occurring, splitting the memcpys is a good choice. I will be trying
> it on my kernels, even if it doesn't get mainlined. Thanks for the idea ;-)
Rather than pulling a number our of our posterior like "every 256 bytes"
which might _really_ screw up performance of some architectures' memcpy
routines, I suspect we might want the platform to provide an optimised
"sleepable_memcpy" function which does it at whatever interval is
appropriate for the memcpy routine in use. Or magically makes it
preemptable. Or uses a DMA engine. Or whatever.
I wonder where else we could use such a function...
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2010-03-19 8:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 16:48 [Patch] fix MTD CFI/LPDDR flash driver huge latency bug Stefani Seibold
2010-03-12 22:23 ` Andrew Morton
2010-03-12 23:38 ` Jamie Lokier
2010-03-13 12:35 ` Stefani Seibold
2010-03-15 3:03 ` Jamie Lokier
2010-03-15 6:15 ` Stefani Seibold
2010-03-15 14:24 ` Jamie Lokier
2010-03-19 8:29 ` David Woodhouse [this message]
2010-03-19 8:40 ` Jamie Lokier
2010-03-13 12:31 ` Stefani Seibold
2010-03-13 11:25 ` Andrew Morton
2010-03-13 17:00 ` Stefani Seibold
-- strict thread matches above, loose matches on Subject: below --
2010-02-28 17:00 Stefani Seibold
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=1268987355.4028.33.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael.kreuzer@nsn.com \
--cc=stefani@seibold.net \
/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).