From: Robert Love <rml@tech9.net>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, mbligh@aracnet.com
Subject: Re: [PATCH] patch-slab-split-03-tail
Date: 04 Oct 2002 17:43:58 -0400 [thread overview]
Message-ID: <1033767839.1247.107.camel@phantasy> (raw)
In-Reply-To: <3D9E0760.8040507@colorfullife.com>
On Fri, 2002-10-04 at 17:25, Manfred Spraul wrote:
> Which cpus have slow local_irq_disable() implementations? At least
> for my Duron, this doesn't seem to be the case [~ 4 cpu cycles
> for cli]
I believe there are pipeline effects to disabling interrupts, e.g. it
has to be flushed?
Robert Love
next prev parent reply other threads:[~2002-10-04 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 17:04 [PATCH] patch-slab-split-03-tail Manfred Spraul
2002-10-04 19:06 ` Andrew Morton
2002-10-04 19:07 ` Martin J. Bligh
2002-10-04 19:15 ` Andrew Morton
2002-10-04 19:15 ` Manfred Spraul
2002-10-04 20:22 ` Randy.Dunlap
2002-10-04 21:25 ` Manfred Spraul
2002-10-04 21:43 ` Robert Love [this message]
2002-10-04 22:30 ` Manfred Spraul
2002-10-05 0:14 ` Anton Blanchard
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=1033767839.1247.107.camel@phantasy \
--to=rml@tech9.net \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mbligh@aracnet.com \
--cc=rddunlap@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