mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Tejun Heo <htejun@gmail.com>, Mikael Pettersson <mikpe@it.uu.se>,
	akpm@linux-foundation.org, david@dgreaves.com,
	jean.luc.coulon@gmail.com, jgarzik@pobox.com,
	michal.k.k.piotrowski@gmail.com, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [REPOST PATCH] sata_promise: use TF interface for polling NODATA commands
Date: Thu, 7 Jun 2007 13:30:27 -0400	[thread overview]
Message-ID: <20070607173027.GC11882@havoc.gtf.org> (raw)
In-Reply-To: <20070607172507.GB11882@havoc.gtf.org>

On Thu, Jun 07, 2007 at 01:25:07PM -0400, Jeff Garzik wrote:
> On Thu, Jun 07, 2007 at 01:20:13PM -0400, Chuck Ebbert wrote:
> > On 06/06/2007 12:05 PM, Jeff Garzik wrote:
> > > FYI to all -- 
> > > 
> > > As a reminder. the Promise hardware programs registers when it receives
> > > a SET FEATURES - XFER MODE.
> > > 
> > > If data transfer is occurring on OTHER ports at the time this is issued,
> > > then data corruption is guaranteed to occur.  Polling will not fix this
> > > problem -- all ports need to be inactive, when a SET FEATURES - XFER
> > > MODE command is issued for any port.
> 
> > So is this patch OK but yet more work needs to be done, or does
> > this patch cause new problems?
> 
> Causes no /new/ problems...  :)  The existing problem described above
> remains.

Just to expand...  this problem doesn't really affect a lot of users in
the majority case, since we do speed tuning before data transfer starts.

The main problem that remains is the rare (but no less important) case
where libata-EH will tune speed during operation in respond to certain
classes of errors.

	Jeff




  reply	other threads:[~2007-06-07 17:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 21:31 Linux 2.6.22-rc4 - sata_promise regression since -rc3 Mikael Pettersson
2007-06-05 21:52 ` Jeff Garzik
2007-06-05 23:37   ` walt
2007-06-06  6:56   ` Tejun Heo
2007-06-06 10:21     ` [REPOST PATCH] sata_promise: use TF interface for polling NODATA commands Tejun Heo
2007-06-06 15:42       ` walt
2007-06-06 16:05       ` Jeff Garzik
2007-06-06 16:34         ` Alan Cox
2007-06-07 17:20         ` Chuck Ebbert
2007-06-07 17:25           ` Jeff Garzik
2007-06-07 17:30             ` Jeff Garzik [this message]
2007-06-07 15:17       ` Jeff Garzik
2007-06-07 15:45         ` Andrew Morton
2007-06-06 11:11 Mikael Pettersson

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=20070607173027.GC11882@havoc.gtf.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=cebbert@redhat.com \
    --cc=david@dgreaves.com \
    --cc=htejun@gmail.com \
    --cc=jean.luc.coulon@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=mikpe@it.uu.se \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®