From: Linus Torvalds <torvalds@linux-foundation.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Andreas Mohr <andi@lisas.de>, Sriram V <vshrirama@gmail.com>,
Pierre Ossman <drzeus-list@drzeus.cx>,
linux-kernel@vger.kernel.org
Subject: Re: Power Management with rootfs on SDMMC.
Date: Sat, 3 Jan 2009 12:23:39 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0901031217261.3179@localhost.localdomain> (raw)
In-Reply-To: <20090102172407.GD1555@ucw.cz>
On Fri, 2 Jan 2009, Pavel Machek wrote:
>
> > (or, slightly reworded: I think it's high time for some kernel God to buy a measly
> > netbook or some such instead of 16-core mainframes to get a feeling for the
> > amount of issues that one hits there)
>
> I have one and yes, its full of problems; see my blog post about 'evil
> little cards'.
Btw, why do people think that CONFIG_USB_PERSIST got removed, and is now
always on? Exactly because of this issue, and because one kernel God (me)
wanted to be able to suspend their netbook.
That said, right now most flash performance is so incredibly bad that I
can't reasonably be expected to use that thing for anything real. They may
say 15-20 MB/s, but that's best-case streaming performance. Real life
write performance is often in the tens of kB (yes, *kilo* bytes) per
second. I hope it will improve, and no, it's not just about ext3 journal
behavior, although that certainly makes some of the issues much much
worse.
So no, I don't use my netbook very much. But this _is_ largely fixed ont
he USB side, even if you may need to do
echo 1 >/sys/bus/usb/devices/.../power/persist
and I argued that we should default to it for any mounted device. It's
hard to do, since the device doesn't even know about whether it's mounted
or not.
Linus
next prev parent reply other threads:[~2009-01-03 20:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 6:35 Sriram V
2009-01-02 10:21 ` Andreas Mohr
2009-01-02 11:21 ` Pierre Ossman
2009-01-02 12:21 ` Andreas Mohr
2009-01-02 17:24 ` Pavel Machek
2009-01-03 20:23 ` Linus Torvalds [this message]
2009-01-03 20:43 ` Pavel Machek
2009-01-03 20:45 ` Alan Cox
2009-01-03 21:16 ` Linus Torvalds
2009-01-03 23:10 ` Alan Cox
2009-01-04 2:59 ` Linus Torvalds
2009-01-04 12:04 ` Alan Cox
2009-01-04 17:53 ` Linus Torvalds
2009-03-29 16:26 ` Andreas Mohr
2009-04-05 18:45 ` Pierre Ossman
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=alpine.LFD.2.00.0901031217261.3179@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=andi@lisas.de \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=vshrirama@gmail.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
all inboxes | Powered by JetHome®