public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Andrew Morton <akpm@osdl.org>
Cc: rmk+lkml@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [MMC] Multi sector write transfers
Date: Thu, 05 Oct 2006 08:42:14 +0200	[thread overview]
Message-ID: <4524A946.1040101@drzeus.cx> (raw)
In-Reply-To: <20061003151034.a7894df8.akpm@osdl.org>

Andrew Morton wrote:
> Russell is moving away from mmc maintainership so we'll need to do
> something different here.
> 
> The patches look good to my untrained eye, except...
> 
> On Sun, 01 Oct 2006 14:42:57 +0200
> Pierre Ossman <drzeus@drzeus.cx> wrote:
> 
>> SD cards extend the protocol by allowing the host to query a card how many
>> blocks were successfully stored on the medium. This allows us to safely write
>> chunks of blocks at once.
> 
> I recall Russell nacked multisector mmc-writing when it came up six or
> twelve months ago.  I don't recall the exact details - lack of trust in
> manufacturers supporting it correctly?
> 
> Is that concern relevant to this patch?

The concern then was that we enabled multi-sector writes across the
board. Russell's concern was that some host controllers weren't properly
reporting back how far they had gotten when a failure occurred. We now
have two solutions to this:

 * Let the drivers set a flag, indicating that the controller properly
reports the number of sent blocks, even when a fault occurs. Russell put
together a patch for this and it is already in Linus' tree.

 * Ask the card, not the controller, how many blocks got there ok. This
is only supported by SD though, so MMC still use only one block per
write (except for the case above).

The only problem I see is if the card has decided to completely shut
down so it's impossible to query the number of blocks written. In this
case, reporting correctly to the upper layers might not be a big issue
(as they can't take any action on the card anyway), so I do not see it
as a problem in practice. I have yet to see any comments on the patch
though (other than end users that like the speed boost).

Rgds
Pierre

      reply	other threads:[~2006-10-05  6:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-01 12:42 [PATCH] [MMC] Multi sector write transfers Pierre Ossman
2006-10-03 22:10 ` Andrew Morton
2006-10-05  6:42   ` 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=4524A946.1040101@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=akpm@osdl.org \
    --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