From: Andi Kleen <ak@suse.de>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory mapped IO vs Port IO
Date: 11 Sep 2003 18:17:02 +0200 [thread overview]
Message-ID: <p73oexri9kx.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <20030911160116.GI21596@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel>
Matthew Wilcox <willy@debian.org> writes:
> There's a lot of drivers in the tree that allow you to access the device
> either via IO port space or IO mem space. Here's some examples:
My gut feeling is to just fix the drivers to make this runtime switchable
and get rid of the compile time options.
This would help distributions (who normally want to build conservative
by default, but still allow the users easy tuning without recompilation)
For that it would be nice if a standard module parameter or maybe
sysfs option existed.
The overhead of checking for PIO vs mmio at runtime in the drivers
should be completely in the noise on any non ancient CPU (both MMIO
and PIO typically take hundreds or thousands of CPU cycles for the bus
access, having an dynamic function call or an if before that is makes
no difference at all)
-Andi
next parent reply other threads:[~2003-09-11 16:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030911160116.GI21596@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel>
2003-09-11 16:17 ` Andi Kleen [this message]
2003-09-11 16:25 ` Matthew Wilcox
2003-09-11 16:31 ` Andi Kleen
2003-09-11 16:42 ` Matthew Wilcox
2003-09-11 17:12 ` Jamie Lokier
2003-09-11 17:25 ` Andi Kleen
2003-09-12 1:39 ` jw schultz
2003-09-12 16:10 ` Anthony Dominic Truong
2003-09-12 16:22 ` Jamie Lokier
2003-09-12 16:27 ` Jesse Barnes
2003-09-12 17:48 ` Jesse Barnes
2003-09-11 17:13 ` Jamie Lokier
[not found] ` <20030911161450.GA23536@sgi.com.suse.lists.linux.kernel>
2003-09-11 16:20 ` Andi Kleen
[not found] <20030911192550.7dfaf08c.ak@suse.de.suse.lists.linux.kernel>
[not found] ` <1063308053.4430.37.camel@huykhoi.suse.lists.linux.kernel>
[not found] ` <20030912162713.GA4852@sgi.com.suse.lists.linux.kernel>
[not found] ` <20030912174807.GA629@sgi.com.suse.lists.linux.kernel>
2003-09-12 18:00 ` Andi Kleen
2003-09-12 18:04 ` Jesse Barnes
2003-09-12 18:09 ` Andi Kleen
2003-09-12 18:11 ` Tim Hockin
2003-09-12 18:24 ` Jesse Barnes
2003-09-12 18:29 ` Andi Kleen
2003-09-12 18:58 ` Martin J. Bligh
2003-09-12 19:51 ` Jesse Barnes
2003-09-12 16:41 John Bradford
2003-09-12 21:52 ` Mike Fedyk
2003-09-13 4:01 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2003-09-11 16:01 Matthew Wilcox
2003-09-11 16:14 ` Måns Rullgård
2003-09-11 16:14 ` Jesse Barnes
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=p73oexri9kx.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.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