public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: "Madhusudhan" <madhu.cr@ti.com>
To: 'Pierre Ossman' <pierre-list@ossman.eu>
Cc: 'Adrian Hunter' <adrian.hunter@nokia.com>, linux-mmc@vger.kernel.org
Subject: RE: MMC retry mechanism
Date: Sun, 6 Sep 2009 12:58:54 -0500	[thread overview]
Message-ID: <004b01ca2f1b$b2ebc9e0$544ff780@am.dhcp.ti.com> (raw)
In-Reply-To: <20090906162041.1f4d939d@mjolnir.ossman.eu>



> -----Original Message-----
> From: Pierre Ossman [mailto:pierre-list@ossman.eu]
> Sent: Sunday, September 06, 2009 9:21 AM
> To: Madhusudhan
> Cc: 'Adrian Hunter'; linux-mmc@vger.kernel.org
> Subject: Re: MMC retry mechanism
> 
> On Fri, 4 Sep 2009 17:08:05 -0500
> "Madhusudhan" <madhu.cr@ti.com> wrote:
> 
> > Hi Adrian,
> >
> > With respect to the below commit, It looks like currently the retry
> > mechanism only handles the READ path.
> >
> > I wonder could a similar retry logic feasible for the WRITE path?
> >
> 
> The claim is that doing so can break some filesystem drivers (notably
> the journaling ones). There has been several threads and patches about
> this in the past.
> 
Okay. Thanks for the info. I would like to read those discussions and the
patches, any reference? Or where do I look for them and any good way to
search such threads in general?

Regards,
Madhu

> Rgds
> --
>      -- Pierre Ossman
> 
>   WARNING: This correspondence is being monitored by the
>   Swedish government. Make sure your server uses encryption
>   for SMTP traffic and consider using PGP for end-to-end
>   encryption.


  reply	other threads:[~2009-09-06 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-04 22:08 MMC retry mechanism Madhusudhan
2009-09-06 14:20 ` Pierre Ossman
2009-09-06 17:58   ` Madhusudhan [this message]
2009-09-14 19:37     ` Pierre Ossman
2009-09-07  7:17 ` Adrian Hunter
2009-09-10 21:20   ` Madhusudhan

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='004b01ca2f1b$b2ebc9e0$544ff780@am.dhcp.ti.com' \
    --to=madhu.cr@ti.com \
    --cc=adrian.hunter@nokia.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=pierre-list@ossman.eu \
    /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