From: Andi Kleen <andi@firstfloor.org>
To: Cliff Wickman <cpw@sgi.com>
Cc: linux-numa@vger.kernel.org
Subject: Re: time for libnuma/numactl 2.0.4 release
Date: Fri, 23 Jul 2010 17:06:31 +0200 [thread overview]
Message-ID: <20100723150631.GD8127@basil.fritz.box> (raw)
In-Reply-To: <E1OcIHL-0007Oq-IU@eag09.americas.sgi.com>
On Fri, Jul 23, 2010 at 08:27:07AM -0500, Cliff Wickman wrote:
>
> Hi linux-numa members,
>
> The last release of libnuma and numactl was 2.0.3, in June 2009.
> Since then there have been 11 patches, in the period Aug2009-May2010.
>
> ftp://oss.sgi.com/www/projects/libnuma/download/numactl-2.0.4-rc3.tar.gz
>
> The patch list since last release:
> 0908 Anton Blanchard libnuma: Fix issue with numactl --hardware on sparse cpumaps
> 0908 Neil Horman libnuma: introduce DSO destructor to free allocated memory
> 0912 Andi Kleen Fix make clean for tests in numactl-2.0.4-rc1
> 1001 Sharyathi Nagesh Fix to numa_node_to_cpus_v2
> 1002 Ian Wienand correct and clarify the numa_node_to_cpus() man page
> 1002 Mike MacCana Correct terminology. ('physical cpus')
> 1004 Lee Schermerhorn Fix libnuma numa_num_{task vs thread}_{cpu|node}s() naming discrepancy
> 1004 Cliff Wickman removed trailing spaces
> 1005 Thomas Renninger Fix CPUless nodes numactl --hardware output
> 1006 Jan Beulich libnuma: enumerate CPUs correctly
> 1006 Jan Beulich libnuma: fix memory corruption
>
> Any missing? Anything to add?
I did a quick test build of the RC and it seems to work. Not done a lot
of testing though.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2010-07-23 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 13:27 time for libnuma/numactl 2.0.4 release Cliff Wickman
2010-07-23 15:06 ` Andi Kleen [this message]
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=20100723150631.GD8127@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=cpw@sgi.com \
--cc=linux-numa@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).