public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: rmk+lkml@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: Multi-sector writes
Date: Wed, 17 Aug 2005 15:56:41 -0700	[thread overview]
Message-ID: <20050817155641.12bb20fc.akpm@osdl.org> (raw)
In-Reply-To: <42FF3C05.70606@drzeus.cx>

Pierre Ossman <drzeus-list@drzeus.cx> wrote:
>
> Adds support for writing multiple sectors at once. This allows
> back-to-back transfers of sectors giving roughly double write throughput.
> 
> To be able to detect which sector is causing problems the system falls
> back to single sector writes if a failure is detected.
> 
> ...
> --- linux-wbsd/drivers/mmc/mmc_block.c	(revision 77)
> +++ linux-wbsd/drivers/mmc/mmc_block.c	(working copy)
> @@ -166,9 +166,25 @@
>  	struct mmc_blk_data *md = mq->data;
>  	struct mmc_card *card = md->queue.card;
>  	int ret;
> +	
> +#ifdef CONFIG_MMC_BULKTRANSFER
> +	int failsafe;
> +#endif
>  
>  	if (mmc_card_claim_host(card))
>  		goto cmd_err;
> +	
> +#ifdef CONFIG_MMC_BULKTRANSFER
> +	/*
> +	 * We first try transfering multiple blocks. If this fails
> +	 * we fall back to single block transfers.
> +	 *
> +	 * This gives us good performance when all is well and the
> +	 * possibility to determine which sector fails when all
> +	 * is not well.
> +	 */
> +	failsafe = 0;
> +#endif
> 

The fact that this is enabled under the experimental
CONFIG_MMC_BULKTRANSFER seems unfortunate.  I mean, if the code works OK
then we should just enable it unconditionally, no?

I'm thinking that it would be better to not have the config option there
and then re-add it late in the 2.6.14 cycle if someone reports problems
which cannot be fixed.  Or at least make it default to 'y' so we get more
testing coverage, then remove the config option later.  Or something.

Thoughts?

  reply	other threads:[~2005-08-17 22:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14 12:41 [PATCH] mmc: Multi-sector writes Pierre Ossman
2005-08-17 22:56 ` Andrew Morton [this message]
2005-08-18  5:48   ` Pierre Ossman
2005-08-18  5:48     ` Andrew Morton
2005-08-18  6:38       ` Russell King
2005-08-18  7:26         ` Pierre Ossman
2005-08-18  8:23           ` Russell King
2005-08-18  8:48             ` Pierre Ossman
2005-08-18 20:19               ` Pavel Machek
2005-08-19  5:00                 ` Pierre Ossman
2005-08-19  7:58                   ` Pavel Machek
2005-08-19  8:12                     ` Pierre Ossman
2005-08-18  9:42           ` Alan Cox
2005-08-18  9:33             ` 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=20050817155641.12bb20fc.akpm@osdl.org \
    --to=akpm@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox