From: "David S. Miller" <davem@redhat.com>
To: ian@ianduggan.net
Cc: alan@lxorguk.ukuu.org.uk, rml@tech9.net, linux-kernel@vger.kernel.org
Subject: Re: 2.4.18 Preempt Freezeups
Date: Fri, 15 Mar 2002 00:51:55 -0800 (PST) [thread overview]
Message-ID: <20020315.005155.93361168.davem@redhat.com> (raw)
In-Reply-To: <3C91B30D.A887A033@ianduggan.net>
In-Reply-To: <3C9153A7.292C320@ianduggan.net> <E16lhBg-0002Yc-00@the-village.bc.nu> <3C91B30D.A887A033@ianduggan.net>
From: Ian Duggan <ian@ianduggan.net>
Date: Fri, 15 Mar 2002 00:38:37 -0800
What is required for preempt beyond "SMP safe" code? I thought the whole
idea was to make the preemptions transparent to other code by utilizing
the SMP critical regions?
Pre-empt makes things like per-cpu data structures require
preemption disables around cpu-local critical regions.
Code that works before just because it knows the data structure is
only even accessed by the current cpu doesn't work because preemption
can cause a context switch at any time.
next prev parent reply other threads:[~2002-03-15 8:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 1:51 2.4.18 Preempt Freezeups Ian Duggan
2002-03-15 1:54 ` Robert Love
2002-03-15 8:36 ` Ian Duggan
2002-03-15 14:25 ` Robert Love
2002-03-15 16:11 ` Mikael Pettersson
2002-03-15 19:11 ` Robert Love
2002-03-16 0:40 ` yodaiken
2002-03-16 1:46 ` Mike Fedyk
2002-03-16 3:12 ` yodaiken
2002-03-17 0:33 ` Daniel Phillips
2002-03-17 1:13 ` yodaiken
2002-03-17 1:14 ` Daniel Phillips
2002-03-17 1:54 ` yodaiken
2002-03-17 2:08 ` Daniel Phillips
2002-03-17 21:17 ` Davide Libenzi
2002-03-15 14:30 ` Alan Cox
2002-03-15 21:36 ` Ian Duggan
2002-03-15 2:11 ` Alan Cox
2002-03-15 8:38 ` Ian Duggan
2002-03-15 8:51 ` David S. Miller [this message]
2002-03-15 14:28 ` Alan Cox
2002-03-16 23:51 ` Daniel Phillips
2002-03-17 3:31 ` Alan Cox
2002-03-17 12:59 ` Dave Jones
2002-03-15 8:43 ` Daniel Phillips
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=20020315.005155.93361168.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ian@ianduggan.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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