All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Robert Hancock <hancockr@shaw.ca>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	ksummit-2008-discuss@lists.linux-foundation.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	linux-ide <linux-ide@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [Ksummit-2008-discuss] Kernel Summit request for Discussion of future of ATA (libata) and IDE
Date: Tue, 05 Aug 2008 08:49:09 +0900	[thread overview]
Message-ID: <48979575.7090004@gmail.com> (raw)
In-Reply-To: <489768A1.8000501@garzik.org>

Jeff Garzik wrote:
> Robert Hancock wrote:
>> Alan Cox wrote:
>>>> * There are still corner case in libata core - PIO is dead slow
>>>> compared to drivers/ide/,
>>> There are two there - libata keeps IRQs blocked for longer in PIO mode as
>>> well which is a factor for realtime that needs looking at, as well as
>>> using 16bit not 32bit I/O for most devices (which is trivial to fix). The
>>> IRQ masking stuff is more complex and old IDE handles it far better for
>>> PIO on non shared IRQ interfaces. That is actually probably the most
>>> complicated thing to address of the stuff you'd want to do if you were
>>> going to kill off old IDE.
>> I was looking into the 32-bit PIO issue a bit yesterday. It looks like 
>> some of the VLB libata drivers are doing this internally already, so it 
>> shouldn't be hard to do this in the core. Only question is how we know 
>> generically if the controller can do it or not? It looks like in old 
>> IDE, a few controllers explicitly disable it, but it appears that it 
>> doesn't default to on for any controller, so it's possible there are 
>> others on which it doesn't work. Presumably anything on an actual 16-bit 
>> bus (ISA, LPC, etc.) wouldn't like it, to start with.
> 
> FWIW there is already a patch from Willy Terreau (sp?) to add 32-bit I/O.
> 
> I queued it for "later" because it had some issues that Alan pointed 
> out, IIRC.  I definitely want to push it in, though.

Jeff, have your thoughts about PIO IRQ disable handling changed yet?  I
don't really see any better way than doing it like IDE.

Thanks.

-- 
tejun

  reply	other threads:[~2008-08-04 23:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.OGeO7gZvBG4obEzRbVltjSebgTQ@ifi.uio.no>
     [not found] ` <fa.KtvYE2B2yrJqUleolhtMPN9ljAQ@ifi.uio.no>
     [not found]   ` <fa.AqEKTvguYFAzDFHy/We/8MpOqmo@ifi.uio.no>
2008-08-04 20:07     ` Kernel Summit request for Discussion of future of ATA (libata) and IDE Robert Hancock
2008-08-04 19:55       ` Alan Cox
2008-08-04 21:17         ` Robert Hancock
2008-08-04 21:06           ` Alan Cox
2008-08-04 21:48             ` Robert Hancock
2008-08-06  0:21             ` Robert Hancock
2008-08-06  0:44               ` Tejun Heo
2008-08-06  2:30                 ` Robert Hancock
2008-08-06 11:27                 ` Sergei Shtylyov
2008-08-06 13:04                   ` [Ksummit-2008-discuss] " Tejun Heo
2008-08-06  8:51               ` Alan Cox
2008-08-04 21:55         ` Sergei Shtylyov
2008-08-04 21:43           ` Alan Cox
2008-08-04 22:45             ` Sergei Shtylyov
2008-08-04 22:52               ` Sergei Shtylyov
2008-08-06 11:17                 ` Sergei Shtylyov
2008-08-04 22:12         ` Mark Lord
2008-08-04 22:00           ` Alan Cox
2008-08-04 20:37       ` Jeff Garzik
2008-08-04 23:49         ` Tejun Heo [this message]
2008-08-03 15:57 James Bottomley
2008-08-03 16:39 ` Alan Cox
2008-08-03 17:32   ` Willy Tarreau
2008-08-03 17:45     ` Rafael J. Wysocki
2008-08-03 20:22       ` [Ksummit-2008-discuss] " David Woodhouse

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=48979575.7090004@gmail.com \
    --to=htejun@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=hancockr@shaw.ca \
    --cc=jeff@garzik.org \
    --cc=ksummit-2008-discuss@lists.linux-foundation.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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.