From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: linux-2.4.10-acX
Date: Tue, 9 Oct 2001 00:01:58 +0000 (UTC) [thread overview]
Message-ID: <9ptepm$134$1@penguin.transmeta.com> (raw)
In-Reply-To: <1002576203.8568.192.camel@phantasy> <E15qi0H-0001xD-00@the-village.bc.nu>
In article <E15qi0H-0001xD-00@the-village.bc.nu>,
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> > getting very hard to merge a lot of the fixes like the truncate standards
>> > compliance stuff so they may not make Linus tree until 2.5
>>
>> What are Linus's complaints about the faster syscall path improvement?
>
>He insisted it wouldnt make it any faster. Of course rdtsc and profiling
>counters of locked cycles show otherwise..
No, I insist that it doesn't make things _noticeably_ faster (a segment
load is something like 12 cycles on a PII), and doing it complicates the
return path unnecessarily for the default case.
I seriously doubt you've (or anybody else) measured it with rdtsc or
profiling: what you call the "fast path" is never taken on regular
system calls, only on nested calls where we return to the kernel. How
many of those have you ever seen?
In short, has _anybody_ EVER seen any actual improvement from this ugly
"optimization"?
Linus
next prev parent reply other threads:[~2001-10-09 0:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 17:40 linux-2.4.10-acX Louis Garcia
2001-10-08 18:07 ` linux-2.4.10-acX Alan Cox
2001-10-08 18:21 ` linux-2.4.10-acX Louis Garcia
2001-10-08 18:29 ` linux-2.4.10-acX Alan Cox
2001-10-08 21:23 ` linux-2.4.10-acX Robert Love
2001-10-08 21:32 ` linux-2.4.10-acX Alan Cox
2001-10-09 0:01 ` Linus Torvalds [this message]
2001-10-08 22:28 ` linux-2.4.10-acX Mike Fedyk
2001-10-08 22:36 ` linux-2.4.10-acX Alan Cox
2001-10-09 0:15 ` linux-2.4.10-acX Greg KH
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='9ptepm$134$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--cc=linux-kernel@vger.kernel.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.