[205] in arla-drinkers
Re: arla on Linux SMP
daemon@ATHENA.MIT.EDU (Aaron M. Ucko)
Fri Aug 14 10:42:53 1998
From owner-arla-drinkers@stacken.kth.se Fri Aug 14 14:42:52 1998
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 19269 invoked from network); 14 Aug 1998 14:42:51 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 14 Aug 1998 14:42:51 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id QAA08723
for arla-drinkers-list; Fri, 14 Aug 1998 16:37:34 +0200 (MET DST)
Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2])
by sundance.stacken.kth.se (8.8.8/8.8.8) with SMTP id QAA08718;
Fri, 14 Aug 1998 16:37:29 +0200 (MET DST)
Received: from MARY-KAY-COMMANDOS.MIT.EDU by MIT.EDU with SMTP
id AA01430; Fri, 14 Aug 98 10:37:05 EDT
Received: by mary-kay-commandos.mit.edu (SMI-8.6/4.7) id KAA27414; Fri, 14 Aug 1998 10:37:21 -0400
To: Magnus Ahltorp <map@stacken.kth.se>
Cc: "A.J.Martin" <A.J.Martin@qmw.ac.uk>, arla-drinkers@stacken.kth.se
Subject: Re: arla on Linux SMP
References: <arla-drinkers:204@unknown-discuss-server>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: amu@mit.edu (Aaron M. Ucko)
Date: 14 Aug 1998 10:37:21 -0400
In-Reply-To: Magnus Ahltorp's message of "14 Aug 1998 13:09:32 +0200"
Message-Id: <udlogtniq8u.fsf@mary-kay-commandos.mit.edu>
Lines: 14
X-Mailer: Gnus v5.6.34/Emacs 20.2
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
<map@stacken.kth.se> (Magnus Ahltorp) writes:
> Do you have a general solution as to when -D__SMP__ should be used and
> when it shouldn't? How do I know that the compilation is done for an
> SMP kernel?
You have to look at the top-level Makefile corresponding to the
kernel. :-( A more reliable approach would be to build one version of
the module suitable for SMP kernels and one suitable for UP kernels,
and have the startup script decide which to load (say, by looking at
/proc/cpuinfo).
--
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)
