From: Andrea Arcangeli <andrea@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: softirq bugs in pre2
Date: Mon, 11 Jun 2001 21:41:33 +0200 [thread overview]
Message-ID: <20010611214133.W5468@athlon.random> (raw)
In-Reply-To: <20010611193703.S5468@athlon.random> <Pine.LNX.4.31.0106111207350.4452-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.31.0106111207350.4452-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Mon, Jun 11, 2001 at 12:09:03PM -0700
On Mon, Jun 11, 2001 at 12:09:03PM -0700, Linus Torvalds wrote:
> The copy-user latency fixes only make sense for out-of-line copies. If
> we're going to have a conditional function call to "schedule()", we do not
> want to inline the dang thing any more - we've just destroyed our register
> set etc anyway.
I think we should override conditional_schedule() with asm, ala
local_bh_enable in pre2, then it should be ok to left the copies inline
(btw I found more bugs in the softirq stuff in pre2, I will keep sorting
it out later today or tomorrow).
Andrea
next prev parent reply other threads:[~2001-06-11 19:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 17:37 softirq bugs in pre2 Andrea Arcangeli
2001-06-11 19:09 ` Linus Torvalds
2001-06-11 19:41 ` Andrea Arcangeli [this message]
2001-06-11 20:55 ` Alan Cox
2001-06-11 22:42 ` Gigabit Intel NIC? - Intel Gigabit Ethernet Pro/1000T Shawn Starr
2001-06-12 16:34 ` Alan Cox
2001-06-12 17:20 ` Riley Williams
2001-06-13 10:25 ` Ion Badulescu
2001-06-13 12:40 ` Ralf Baechle
2001-06-13 17:07 ` James Sutherland
2001-06-14 20:59 ` Riley Williams
2001-06-14 21:10 ` Jeff Garzik
2001-06-14 21:14 ` Matthew Jacob
2001-06-14 21:29 ` Alan Cox
2001-06-14 21:52 ` Matthew Dharm
2001-06-14 21:58 ` Alan Cox
2001-06-14 22:03 ` Matthew Jacob
2001-06-15 2:20 ` Shawn Starr
2001-06-12 2:54 ` softirq bugs in pre2 Andrew Morton
2001-06-11 21:58 ` Pavel Machek
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=20010611214133.W5468@athlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.