All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Pierre Ossman <drzeus-list@drzeus.cx>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: MMC performance
Date: Mon, 11 Oct 2004 14:18:45 +0100	[thread overview]
Message-ID: <1097500722.31259.17.camel@localhost.localdomain> (raw)
In-Reply-To: <20041011131919.B19175@flint.arm.linux.org.uk>

On Llu, 2004-10-11 at 13:19, 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.

Only on retries. You can try and blast the lot out the first time then
on retries you write sector by sector.



  reply	other threads:[~2004-10-11 14:22 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 [this message]
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

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=1097500722.31259.17.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.