From: Tejun Heo <htejun@gmail.com>
To: Alexander Trotsai <mage@adamant.ua>
Cc: John Lash <jkl@sarvega.com>, lkml <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: sata_sil Mod15Write quirk workaround patch for vanilla kernel avaialble.
Date: Mon, 04 Apr 2005 16:57:25 +0900 [thread overview]
Message-ID: <4250F365.9020701@gmail.com> (raw)
In-Reply-To: <20050404071002.GI4383@blackhole.adamant.ua>
Alexander Trotsai wrote:
> On Fri, Apr 01, 2005 at 07:51:28AM +0900, Tejun Heo wrote:
> TH> Hello, John.
> TH>
> TH> John Lash wrote:
> TH> >On Fri, 01 Apr 2005 00:01:23 +0900
> TH> >Tejun Heo <htejun@gmail.com> wrote:
> TH> >
> TH> >
> TH> >>Hello, guys.
> TH> >>
> TH> >>I generated m16w workaround patch for 2.6.11.6 (by just removing two
> TH> >>lines :-) and set up a page regarding m15w quirk and the workaournd.
> TH> >>I'm planning on updating m15w patch against the vanilla tree until it
> TH> >>gets into the mainline so that impatient users can try out and it gets
> TH> >>more testing.
> TH> >>
> TH> >>http://home-tj.org/m15w
> TH> >>
> TH> >>Thanks.
> TH> >>
> TH> >>--
> TH> >>tejun
> TH> >>
> TH> >
> TH> >
> TH> >Tejun,
> TH> >
> TH> >I applied the patch to a clean 2.6.11.6 kernel and got an unresolved
> TH> >symbol error for "ATA_TFLAG_LBA". I tried changing that to
> TH> >"ATA_TFLAG_LBA48" and
> TH> >it compiles and runs.
> TH> >
> TH> >So far, no problems. Thanks a lot for the patch.
> TH>
> TH> I'm sorry. I uploaded the original patch against libata-dev-2.6 tree.
> TH> The two BUG_ON() lines should just be removed. I've uploaded fixed
> TH> patch. Thanks for pointing out.
>
> Thanks
> Seems to be worked (I'm install with ide-ata-2.6 patch)
> But with heavy read load write performance is very very bad
> (near 50-100 KBps)
> But I think that is not problem of Silicon card (I have also
> to SATA hard drives on Intel onboard SATA controller with
> same performance troubles)
It has been quite a while since I looked at the elevator code but,
IIRC, anticipatory elevator (rightfully) favors read requests over
writes and doesn't care much about fairness between processes (IOW,
request streams). It depends on your workload but try using cfq. For
many puposes including common desktop usage, I find cfq to be better suited.
Thanks.
--
tejun
prev parent reply other threads:[~2005-04-04 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 15:01 sata_sil Mod15Write quirk workaround patch for vanilla kernel avaialble Tejun Heo
2005-03-31 17:10 ` John Lash
2005-03-31 22:51 ` Tejun Heo
2005-04-04 7:10 ` Alexander Trotsai
2005-04-04 7:57 ` Tejun Heo [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=4250F365.9020701@gmail.com \
--to=htejun@gmail.com \
--cc=jkl@sarvega.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mage@adamant.ua \
/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;
as well as URLs for NNTP newsgroup(s).