All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Cc: lse-tech@lists.sourceforge.net, kaos@ocs.com.au,
	James.Bottomley@steeleye.com, mort@wildopensource.com,
	davidm@napali.hpl.hp.com, jun.nakajima@intel.com,
	tomita@cinet.co.jp
Subject: cpu-2.5.69-bk14-1
Date: Tue, 20 May 2003 10:03:31 -0700	[thread overview]
Message-ID: <20030520170331.GK29926@holomorphy.com> (raw)

Extended cpumasks for larger systems. Now featuring bigsmp, Summit,
and Voyager updates in addition to PC-compatible, NUMA-Q, and SN2
bits from SGI.

Several minor bugfixes with improper checks of bits and some new
API pieces: cpumask_of_cpu() and cpus_promote() for replacing
1 << cpu and promoting "narrow" cpumasks (i.e. unsigned long) to
full-width, respectively.

Successfully runs on 32x NUMA-Q. Successfully compiletested on Voyager,
Summit, bigsmp, and flat logical SMP, all with typechecking. UP also
successfully compiletested with and without local APIC and IO-APIC.
Hopefully I can get my hands on another NUMA-Q quad or two soon.

vs. 2.5.69-bk14. The patch (too large to post) can be found at
ftp://ftp.kernel.org/pub/linux/kernel/people/wli/cpu/cpu-2.5.69-bk14-1.bz2

I'd be much obliged if (sub)arch maintainers could comment.

Tomita, I didn't have a way of building PC98; if you are negatively
affected somehow I'm interested in hearing of how to fix things up
or any other special handling PC98 might need here.

David & Martin, I'm not 100% sure wrt. what's going on with the IA64
pieces of the puzzle. The more I find out about what you want, the
better.

Thanks.


-- wli

             reply	other threads:[~2003-05-20 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 17:03 William Lee Irwin III [this message]
2003-05-21  8:43 ` [Lse-tech] cpu-2.5.69-bk14-1 Christoph Hellwig
2003-05-21 15:23   ` William Lee Irwin III
2003-05-21 15:05 ` Martin J. Bligh
2003-05-24 21:54 ` cpu-2.5.69-bk14-1 Zwane Mwaikambo
2003-05-25  4:23   ` cpu-2.5.69-bk14-1 William Lee Irwin III
2003-05-25  4:39     ` cpu-2.5.69-bk14-1 Zwane Mwaikambo

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=20030520170331.GK29926@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=davidm@napali.hpl.hp.com \
    --cc=jun.nakajima@intel.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=mort@wildopensource.com \
    --cc=tomita@cinet.co.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.