From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: MMC performance
Date: Mon, 11 Oct 2004 15:49:19 +0200 [thread overview]
Message-ID: <416A8F5F.6000000@drzeus.cx> (raw)
In-Reply-To: <20041011131919.B19175@flint.arm.linux.org.uk>
Russell King wrote:
>Only if you can reliably know how many bytes you've tranferred when
>an error occurs. Without that, the only safe way to do a write is
>sector by sector.
>
>
>
What would happen if we failed the entire request? Rewriting a few
sectors is harmless. Or will it break in more exotic ways?
Rgds
Pierre
prev parent reply other threads:[~2004-10-11 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 11:05 MMC performance Pierre Ossman
2004-10-11 12:19 ` Russell King
2004-10-11 13:18 ` Alan Cox
2004-10-11 15:27 ` Pierre Ossman
2004-10-11 18:01 ` Pierre Ossman
2004-10-18 19:26 ` Pierre Ossman
2004-10-11 13:49 ` Pierre Ossman [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=416A8F5F.6000000@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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