From: Alan <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sata_via: PATA support, resubmit
Date: Mon, 8 Jan 2007 15:42:49 +0000 [thread overview]
Message-ID: <20070108154249.6d8f5697@localhost.localdomain> (raw)
In-Reply-To: <45A24159.7060001@pobox.com>
> The problem you need to fix or work around is ata_probe_ent, which
> doesn't properly fill in ata_port info for this situation. Tejun has
> posted patches that kill ata_probe_ent, which you were pointed to.
And which are not yet in the main tree leaving many users unable to
install Linux. This isn't the way to get stuff done. When you've got the
new patches in the driver can use them if its worth it (which, see below,
I question).
> If you get the setup right, you don't bloat each hook with "is this port
> PATA?" tests. At present, your sata_via patch introduces these needless
> tests.
Which I might note are actually smaller than the extra structs and on a
code path usually executed twice per boot. So the needless tests are more
efficient and not on a hot path and are shorter than the elegant
not-present solution and let users actually install Linux on current VIA
systems, which right now the generally cannot do.
Out of boredom I'll also note that clock timings say that if the extra
port info stuff causes a single extra L1 cache miss its also faster to do
the tests.
Alan
next prev parent reply other threads:[~2007-01-08 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 12:26 Alan
2007-01-08 13:04 ` Jeff Garzik
2007-01-08 15:42 ` Alan [this message]
2007-01-08 15:51 ` Jeff Garzik
2007-01-08 16:40 ` Alan
2007-01-08 16:34 ` Jeff Garzik
2007-01-08 17:11 ` Alan
2007-01-09 10:39 ` 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=20070108154249.6d8f5697@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--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
Powered by JetHome