From: Randy Dunlap <rdunlap@xenotime.net>
To: "Joshua Hintze" <joshh@imsar.com>
Cc: "'Maxim Levitsky'" <maximlevitsky@gmail.com>,
<linux-kernel@vger.kernel.org>, <linux-ide@vger.kernel.org>
Subject: Re: PATA IDE is slower in newer versions of kernel
Date: Sat, 18 Sep 2010 12:47:50 -0700 [thread overview]
Message-ID: <20100918124750.393a64a8.rdunlap@xenotime.net> (raw)
In-Reply-To: <010d01cb5769$cbca3380$635e9a80$@com>
On Sat, 18 Sep 2010 13:43:40 -0600 Joshua Hintze wrote:
> Thanks,
>
> I'm not sure what you mean by bisect, other than just the definition of the word. I am breaking this problem down adding printks etc. I think I'm finally beginng to understand how this works :)
>
http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#using-bisect
>
>
> -----Original Message-----
> From: linux-ide-owner@vger.kernel.org [mailto:linux-ide-owner@vger.kernel.org] On Behalf Of Maxim Levitsky
> Sent: Saturday, September 18, 2010 1:23 PM
> To: Joshua Hintze
> Cc: linux-kernel@vger.kernel.org; linux-ide@vger.kernel.org
> Subject: RE: PATA IDE is slower in newer versions of kernel
>
> On Sat, 2010-09-18 at 11:12 -0600, Joshua Hintze wrote:
> > Some updated information. I created a screen capture of what I am seeing. First is the logic analyzer when the newer linux kernel is writing slow to the PATA port.
> >
> > http://i56.tinypic.com/oqhrug.png
> >
> > Notice in the above link how there is a lot of activating and then large gaps of no activity. After about 9 mS the STOP line is strobed a few times and then DMARQ finally returns to normal operating. The link below shows the picture of an old 2.6.10 kernel where write speeds are much faster.
> >
> > http://i51.tinypic.com/a9wiur.png
> >
> > In the above image notice how the wait time is considerable less 100's of microseconds before the stop lines get strobed.
> >
> > I'm dedicated to continue working on the problem, I just need to advice from the linux community. I've tried different I/O schedulers such as noop and anticipatory and I'm studying the ide-dma code but still lost to where this is happening.
> >
> > Thanks!
> >
> Maybe you can just bisect this?
> Just a general advice, I don't know ide subsystem at all.
>
> Best regards,
> Maxim Levitsky
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-09-18 19:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 23:30 Joshua Hintze
2010-09-17 13:47 ` Alejandro Riveira Fernández
2010-09-18 17:12 ` Joshua Hintze
2010-09-18 19:22 ` Maxim Levitsky
2010-09-18 19:43 ` Joshua Hintze
2010-09-18 19:47 ` Randy Dunlap [this message]
2010-09-18 20:02 ` Joshua Hintze
2010-09-18 20:04 ` Arnd Bergmann
2010-09-19 0:59 ` Alan Cox
2010-09-19 4:23 ` Joshua Hintze
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=20100918124750.393a64a8.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=joshh@imsar.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
/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®