From: Davide Libenzi <davidel@xmailserver.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Linus Torvalds <torvalds@osdl.org>,
Andy Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] lazy I/O bitmap copy for i386 (ver 2) ...
Date: Tue, 24 Aug 2004 13:04:15 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0408241246040.3219@bigblue.dev.mdolabs.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408241113370.2026@bigblue.dev.mdolabs.com>
On Tue, 24 Aug 2004, Davide Libenzi wrote:
> The following patch implements the lazy I/O bitmap copy for the i386
> architecture. It uses an invalid bitmap offset inside the TSS to eventually
> handle the correct bitmap update in the GPF handler. The logic is the same
> of the first version, plus the usage of get/put_cpu() (thx Brian) and the
> nesting over the latest Ingo variable bitmap bits.
As followup, I instrumented the switchto code to do something like:
if (prev->io_bitmap_ptr) {
if (tss->io_bitmap_base == INVALID_IO_BITMAP_OFFSET_LAZY)
no_hit_gpf++;
else
hit_gpf++;
}
After a couple of minutes of light X usage I get:
Hit: 1017
NoHit: 29541
This is FC1 up-to-date (yesterday's ~60% rate was due an incorrect test
performed in the instrumentation code). Did not run any perf test, but for
sure updating an unsigned long should result faster than memcpy/memset
memory regions, during context switches.
- Davide
next prev parent reply other threads:[~2004-08-24 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 18:20 Davide Libenzi
2004-08-24 20:04 ` Davide Libenzi [this message]
2004-08-31 12:06 ` 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=Pine.LNX.4.58.0408241246040.3219@bigblue.dev.mdolabs.com \
--to=davidel@xmailserver.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®