All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: jgarzik@pobox.com, linux-ide@vger.kernel.org, htejun@gmail.com
Subject: [PATCHSET] sata_sil: implement Mod15Write workaround by split request processing
Date: Thu, 19 Oct 2006 14:51:38 +0900	[thread overview]
Message-ID: <1161237098656-git-send-email-htejun@gmail.com> (raw)
In-Reply-To: 

Hello, Jeff.

This is updated version of the Mod15Write workaround I've been
maintaining for a year now.  This patchset contains the following
patches.

#01-03 : Prepare libata for m15w workaround.  All three patches are
	 justifiable by themselves.
#04    : implement Mod15Write workaround by split request processing

The core split processing code is in production use on many machines
and I haven't heard about malfucntion for a very long time, so I
suppose they're pretty stable.

For mainline inclusion, I've added code to handle PIO mode.  When the
device is switched to PIO mode, sata_sil turns of split request
processing and limits max_sectors to 15 and vice versa when it exits
PIO mode.

This patchset is against the current #upstream
(da54f5fe54c7d75e2db7d17961fb36a8c28a8501).

Thanks.

--
tejun



             reply	other threads:[~2006-10-19  5:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19  5:51 Tejun Heo [this message]
2006-10-19  5:51 ` [PATCH 1/4] libata: implement ATA_EHI_PRINTINFO Tejun Heo
2006-11-01  1:57   ` Jeff Garzik
2006-10-19  5:51 ` [PATCH 4/4] sata_sil: implement Mod15Write workaround by split request processing Tejun Heo
2006-11-01  1:59   ` Jeff Garzik
2006-11-01  2:17     ` Tejun Heo
2006-11-01  2:31       ` Jeff Garzik
2006-11-01  9:16         ` Tejun Heo
2006-10-19  5:51 ` [PATCH 2/4] libata: implement ATA_EHI_SETMODE and ATA_EHI_POST_SETMODE Tejun Heo
2006-10-19  5:51 ` [PATCH 3/4] libata: move dev->max_sectors configuration into ata_dev_configure() Tejun Heo

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=1161237098656-git-send-email-htejun@gmail.com \
    --to=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.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 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.