linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Daniel Phillips <phillips@arcor.de>
Cc: Rik van Riel <riel@conectiva.com.br>,
	Richard.Zidlicky@stud.informatik.uni-erlangen.de,
	zippel@linux-m68k.org, linux-m68k@lists.linux-m68k.org,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4 mm trouble [possible lru race]
Date: Tue, 1 Oct 2002 20:04:42 +0200	[thread overview]
Message-ID: <20021001180442.GI5755@suse.de> (raw)
In-Reply-To: <E17wRKZ-0005vf-00@starship>

On Tue, Oct 01 2002, Daniel Phillips wrote:
> On Tuesday 01 October 2002 19:31, Jens Axboe wrote:
> > On Tue, Oct 01 2002, Daniel Phillips wrote:
> > > On Tuesday 01 October 2002 18:56, Rik van Riel wrote:
> > > > On Tue, 1 Oct 2002, Daniel Phillips wrote:
> > > > > On Tuesday 01 October 2002 16:20, Richard.Zidlicky@stud.informatik.uni-erlangen.de wrote:
> > > > > > no preempt or anything fancy, m68k vanila 2.4.19 (well almost).
> > > > >
> > > > > Vanilla would be CONFIG_SMP=y, is that what you have?
> > > > 
> > > > Somehow I doubt Linux supports m68k SMP machines ;)
> > > 
> > > CONFIG_SMP=y works perfectly well on single cpu machines - it forces
> > > the spinlocks to actually exist.  It's not supposed to change any
> > > behaviour, but you never know.  Behaviour is obviously changing here.
> > 
> > Again, m68k was the target.
> 
> Sure fine, no good reason to be cryptic about it though.
> 
>    #error "m68k doesn't do SMP yet"
> 
> So SMP must be off or the compile would abort.  Well, the only interesting

There's no CONFIG_SMP in the m68k arch config.in. Anyways, enough
beating of dead horse :)

-- 
Jens Axboe


  reply	other threads:[~2002-10-01 18:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01 14:20 Richard.Zidlicky
2002-10-01 15:12 ` Daniel Phillips
2002-10-01 15:29 ` Daniel Phillips
2002-10-01 16:56   ` Rik van Riel
2002-10-01 17:10     ` Daniel Phillips
2002-10-01 17:31       ` Jens Axboe
2002-10-01 18:01         ` Daniel Phillips
2002-10-01 18:04           ` Jens Axboe [this message]
2002-10-01 18:14             ` Daniel Phillips
2002-10-01 18:22               ` Rik van Riel
2002-10-02 12:07               ` Geert Uytterhoeven
2002-10-02  9:45           ` Richard Zidlicky
  -- strict thread matches above, loose matches on Subject: below --
2002-10-20 14:37 Richard Zidlicky
     [not found] <20020925122439.C198@linux-m68k.org>
     [not found] ` <Pine.LNX.4.44.0209281634240.338-100000@serv>
     [not found]   ` <20021001112229.A235@linux-m68k.org>
2002-10-01 10:26     ` 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=20021001180442.GI5755@suse.de \
    --to=axboe@suse.de \
    --cc=Richard.Zidlicky@stud.informatik.uni-erlangen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=phillips@arcor.de \
    --cc=riel@conectiva.com.br \
    --cc=zippel@linux-m68k.org \
    --subject='Re: 2.4 mm trouble [possible lru race]' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).