public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	mingo@elte.hu, bunk@kernel.org, astarikovskiy@suse.de,
	tglx@linutronix.de, James.Bottomley@HansenPartnership.com,
	linux-kernel@vger.kernel.org
Subject: Re: Voyager phys_cpu_present_map compile error
Date: Tue, 22 Apr 2008 16:25:09 +0100	[thread overview]
Message-ID: <20080422152509.GE26446@shadowen.org> (raw)
In-Reply-To: <20080422062927.bb360a36.akpm@linux-foundation.org>

On Tue, Apr 22, 2008 at 06:29:27AM -0700, Andrew Morton wrote:
> > On Mon, 21 Apr 2008 08:55:36 -0400 "H. Peter Anvin" <hpa@zytor.com> wrote:
> >
> > If there are no VISWS' left, we should just unload the code.
> 
> yup, it's a desirable objective.
> 
> I have a suspicion that there are no NUMAQs left either.  Andy, would it be
> missed?

Cirtainly these boxes are getting near end-of-life.  I am not sure how
many are out there beyond our the ones we have in the lab.  We do
maintain regular testing on them, even reporting them to TKO.

The main reason we bother keeping them working is that they have a large
numa ratio and tend to show up issues with other things, like the numa
scheduler issues when we got that latest re-write.

I has always been a shame that support wasn't included in generic, and
as a result we have ended up with this three way split "generic, voyager,
and numaq".  It made sense at the time for developers, but never did for
those down the food chain; particularly for distros.

-apw

  reply	other threads:[~2008-04-22 15:25 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21  0:02 Voyager phys_cpu_present_map compile error Adrian Bunk
2008-04-21  8:53 ` Adrian Bunk
2008-04-21 12:00   ` Ingo Molnar
2008-04-21 12:55     ` H. Peter Anvin
2008-04-21 14:10       ` Status of SGI 320/540 (Visual Workstation) support? Adrian Bunk
2008-04-22  6:19         ` Andrey Panin
2008-04-22 13:29       ` Voyager phys_cpu_present_map compile error Andrew Morton
2008-04-22 15:25         ` Andy Whitcroft [this message]
2008-04-21 13:00     ` H. Peter Anvin
2008-04-21 15:42       ` James Bottomley
2008-04-21 20:03         ` Ingo Molnar
2008-04-21 23:08           ` James Bottomley
2008-04-21 19:55       ` Ingo Molnar
2008-04-21 20:03         ` H. Peter Anvin
2008-04-21 20:11           ` Ingo Molnar
2008-04-21 20:10             ` H. Peter Anvin
2008-04-23  8:53             ` Pavel Machek
2008-04-21 13:27     ` Adrian Bunk
2008-04-21 20:14       ` Ingo Molnar
2008-04-21 21:57         ` James Bottomley
2008-04-25 14:50         ` James Bottomley
2008-04-25 16:17           ` Adrian Bunk
2008-04-25 16:33             ` James Bottomley
2008-04-28 17:59               ` Ingo Molnar
2008-04-28 19:09                 ` James Bottomley
2008-04-21 15:58     ` James Bottomley
2008-04-21 19:51       ` Ingo Molnar
2008-04-21 20:09         ` Adrian Bunk
2008-04-21 20:13           ` Ingo Molnar
2008-04-21 20:26             ` Adrian Bunk
2008-04-21 20:29               ` Ingo Molnar
2008-04-21 21:02                 ` Adrian Bunk
2008-04-21 22:31                   ` Ingo Molnar
2008-04-26  7:43                     ` Pavel Machek
2008-04-27  0:44                       ` H. Peter Anvin
2008-04-27  1:06                         ` Adrian Bunk
2008-04-27  1:45                           ` H. Peter Anvin

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=20080422152509.GE26446@shadowen.org \
    --to=apw@shadowen.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=astarikovskiy@suse.de \
    --cc=bunk@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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