From: Arjan van de Ven <arjanv@redhat.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andy Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch] lazy TSS's I/O bitmap copy ...
Date: Tue, 24 Aug 2004 08:51:12 +0200 [thread overview]
Message-ID: <1093330271.2792.3.camel@laptop.fenrus.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408231311460.3221@bigblue.dev.mdolabs.com>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
On Mon, 2004-08-23 at 23:23, Davide Libenzi wrote:
> The following patch implements a lazy I/O bitmap copy for the i386
> architecture. With I/O bitmaps now reaching considerable sizes, if the
> switched task does not perform any I/O operation, we can save the copy
> altogether. In my box X is working fine with the following patch, even if
> more test would be required.
the thing is that X will not hit your fault path, since it runs with
iopl() called... your patch is a nice optimisation for X as a result,
however as test, X is almost worthless ;(
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-24 6:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 21:23 [patch] lazy TSS's I/O bitmap copy Davide Libenzi
2004-08-23 21:32 ` Andi Kleen
2004-08-23 21:39 ` Davide Libenzi
2004-08-23 22:07 ` Linus Torvalds
2004-08-23 22:18 ` Davide Libenzi
2004-08-23 22:27 ` Linus Torvalds
2004-08-28 19:15 ` Alan Cox
2004-08-23 22:54 ` Davide Libenzi
2004-08-23 23:09 ` Linus Torvalds
2004-08-23 23:33 ` Davide Libenzi
2004-08-24 7:19 ` [patch] ioport-cache-2.6.8.1.patch Ingo Molnar
2004-08-24 15:15 ` Davide Libenzi
2004-08-24 19:38 ` Ryan Cumming
2004-08-24 20:20 ` Ingo Molnar
2004-08-24 1:53 ` [patch] lazy TSS's I/O bitmap copy Brian Gerst
2004-08-24 2:17 ` Linus Torvalds
2004-08-24 4:30 ` Davide Libenzi
2004-08-24 6:51 ` Arjan van de Ven [this message]
2004-08-24 15:13 ` Davide Libenzi
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=1093330271.2792.3.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=davidel@xmailserver.org \
--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 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.