From: "Kevin Radloff" <radsaq@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, "Tejun Heo" <htejun@gmail.com>,
jgarzik@pobox.com, torvalds@osdl.org
Subject: Re: PATCH: Fix broken PIO with libata
Date: Tue, 16 May 2006 11:33:27 -0400 [thread overview]
Message-ID: <3b0ffc1f0605160833k5f6355c5n3f2a9ab1b211a95@mail.gmail.com> (raw)
In-Reply-To: <1147790393.2151.62.camel@localhost.localdomain>
On 5/16/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> The revaldiation in 2.6.17-rc has broken support for PIO only devices.
> This is fairly unusual in the SATA world but showed up rather more
> promptly with the added PATA drivers.
Excellent; this seems to have solved my oops on CF card insertion problem. :)
However, I still have a problem with pata_pcmcia (that I actually
experienced also with the ide-cs driver) where sustained reading or
writing to the CF card spikes the CPU with nearly 100% system time.
Here's a few seconds of 'vmstat 5' with a 'cat /dev/sdb > /dev/null'
in the middle of it:
procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
r b swpd free buff cache si so bi bo in cs us sy id wa
1 1 0 502608 13304 254740 0 0 164 42 1089 618 7 2 85 5
1 1 0 495440 20472 254740 0 0 1434 7 1078 1079 1 95 0 4
1 1 0 487264 28664 254740 0 0 1638 8 1073 1063 1 95 0 4
1 1 0 479940 35832 254740 0 0 1434 50 1077 1087 1 95 0 4
1 1 0 472320 43000 254740 0 0 1434 15 1078 1093 10 86 0 4
1 1 0 465104 50168 254740 0 0 1434 56 1077 1053 6 90 0 4
1 1 0 456944 58360 254740 0 0 1638 8 1072 1063 1 94 0 5
1 1 0 449744 65528 254740 0 0 1434 3 1073 1069 1 94 0 5
1 1 0 441600 73720 254740 0 0 1638 5 1072 1071 1 95 0 4
1 1 0 434020 80888 254740 0 0 1434 0 1074 1087 11 85 0 4
0 0 0 428896 86008 254740 0 0 1024 3 1184 1313 4 83 11 3
0 0 0 428896 86008 254740 0 0 0 5 1105 1057 1 0 98 0
--
Kevin 'radsaq' Radloff
radsaq@gmail.com
http://thesaq.com/
next prev parent reply other threads:[~2006-05-16 15:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 14:39 Alan Cox
2006-05-16 15:33 ` Kevin Radloff [this message]
2006-05-16 15:53 ` Alan Cox
2006-05-16 17:19 ` Kevin Radloff
2006-05-16 17:27 ` Jeff Garzik
2006-05-16 17:39 ` Tejun Heo
2006-05-16 18:13 ` Kevin Radloff
2006-05-16 22:51 ` Alan Cox
2006-05-16 15:36 ` Tejun Heo
2006-05-16 15:48 ` Jeff Garzik
2006-05-16 15:57 ` Tejun Heo
2006-05-16 23:00 ` Paul Mackerras
2006-05-16 17:10 ` Jeff Garzik
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=3b0ffc1f0605160833k5f6355c5n3f2a9ab1b211a95@mail.gmail.com \
--to=radsaq@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®