From: Robert Love <rml@tech9.net>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] syscall latency improvement #1
Date: 25 Jan 2002 17:35:19 -0500 [thread overview]
Message-ID: <1011998120.3505.29.camel@phantasy> (raw)
In-Reply-To: <18993.1011984842@warthog.cambridge.redhat.com>
In-Reply-To: <18993.1011984842@warthog.cambridge.redhat.com>
On Fri, 2002-01-25 at 13:54, David Howells wrote:
> The attached patch does the following to 2.5.3-pre5:
>
> * consolidates various status items that are found in the lower reaches of
> task_struct into one 32-bit word, thus allowing them to be tested
> atomically without the need to disable interrupts in entry.S.
>
> * optimises the instructions in the system_call path in entry.S
>
> * frees up a hole in the bottom part of the task_struct (on the 1st cache
> line).
>
> * improves base syscall latency by approximately 5.4% (dual PIII) or 3.6%
> (dual Athlon) as measured by lmbench's "lat_syscall null" command against
> the vanilla kernel.
Mmm, I like it. Ingo Molnar talked to me about this (he wants such a
feature, too) earlier. This is a real win.
This patch is beneficial to the kernel preemption patch. I suspect
other future ideas could be added now without hurting the common case,
too. I had planned to roll need_resched into our preemption counter,
and I probably still can even with only 1 byte.
Anyhow, I'm looking it over -- good code.
Robert Love
next prev parent reply other threads:[~2002-01-25 22:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 18:54 [PATCH] syscall latency improvement #1 David Howells
2002-01-25 22:35 ` Robert Love [this message]
2002-01-26 10:07 ` Nigel Gamble
2002-01-25 23:07 ` Paul Mackerras
2002-01-26 0:39 ` Linus Torvalds
2002-01-26 0:57 ` Andrew Morton
2002-01-26 1:20 ` Linus Torvalds
2002-01-26 4:00 ` Jamie Lokier
2002-01-28 14:18 ` Denis Vlasenko
2002-01-28 10:30 ` Andrew Morton
2002-01-28 15:28 ` Jeff Dike
2002-01-29 0:53 ` Rusty Russell
2002-01-29 12:54 ` Pavel Machek
2002-01-29 12:59 ` Denis Vlasenko
2002-02-21 7:10 ` Cameron Simpson
2002-01-26 18:39 ` [PATCH] " Alan Cox
2002-01-27 19:59 ` Jamie Lokier
[not found] <18993.1011984842@warthog.cambridge.redhat.com.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.33.0201251626490.2042-100000@penguin.transmeta.com.suse.lists.linux.kernel>
2002-01-26 1:24 ` Andi Kleen
2002-01-26 1:53 ` Linus Torvalds
2002-01-26 2:03 ` Andi Kleen
2002-01-26 2:14 ` Linus Torvalds
2002-01-26 2:26 ` Andi Kleen
2002-01-26 2:39 ` Dave Jones
2002-01-26 2:53 ` Davide Libenzi
2002-01-26 2:10 ` Andrew Morton
2002-01-26 3:06 ` Robert Love
2002-01-26 3:20 ` Robert Love
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=1011998120.3505.29.camel@phantasy \
--to=rml@tech9.net \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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