From: Ryan Cumming <ryan@spitfire.gotdns.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: "David S. Miller" <davem@redhat.com>, Ingo Molnar <mingo@elte.hu>,
torvalds@osdl.org, Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] context-switching overhead in X, ioport(), 2.6.8.1
Date: Sat, 21 Aug 2004 23:06:12 -0700 [thread overview]
Message-ID: <200408212306.15012.ryan@spitfire.gotdns.org> (raw)
In-Reply-To: <1093154401.817.43.camel@krustophenia.net>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
On Saturday 21 August 2004 23:00, Lee Revell wrote:
> On Sun, 2004-08-22 at 01:42, Ryan Cumming wrote:
> > On Saturday 21 August 2004 21:46, David S. Miller wrote:
> > > FWIW, I would recommend a sparse bitmap implementation for the
> > > ioport stuff.
> >
> > The problem is that the sparse bitmap would have to be unpacked to the
> > "dense" bitmap that lives in the TSS on context switch.
>
> Can someone supply a link to the original LKML post with the ioport
> change? I was not able to find it in my mailbox nor in the archives.
Here's what I could dig up:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7/2.6.7-mm2/broken-out/larger-io-bitmap.patch
http://www.uwsg.iu.edu/hypermail/linux/kernel/0211.0/0477.html
http://www.uwsg.iu.edu/hypermail/linux/kernel/9807.1/1079.html
Looks like x86-64 does in fact need a similar change to the x86 one. It's late
here, but it should be pretty trivial to port over.
-Ryan
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-22 6:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 13:55 [patch] context-switching overhead in X, ioport(), 2.6.8.1 Ingo Molnar
2004-08-22 4:46 ` David S. Miller
2004-08-22 5:42 ` Ryan Cumming
2004-08-22 6:00 ` Lee Revell
2004-08-22 6:06 ` Ryan Cumming [this message]
[not found] <2vEzI-Vw-17@gated-at.bofh.it>
2004-08-22 12:16 ` Andi Kleen
2004-08-22 12:00 ` Alan Cox
2004-08-22 14:23 ` Andi Kleen
2004-08-22 14:47 ` Alan Cox
2004-08-22 17:31 ` Ingo Molnar
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=200408212306.15012.ryan@spitfire.gotdns.org \
--to=ryan@spitfire.gotdns.org \
--cc=akpm@osdl.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
--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 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.