From: William Lee Irwin III <wli@holomorphy.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: NUMA API
Date: Fri, 30 Apr 2004 01:30:17 -0700 [thread overview]
Message-ID: <20040430083017.GB1298@holomorphy.com> (raw)
In-Reply-To: <409201BE.9000909@redhat.com>
On Fri, Apr 30, 2004 at 12:35:26AM -0700, Ulrich Drepper wrote:
> In the last weeks I have been working on designing a new API for a NUMA
> support library. I am aware of the code in libnuma by ak but this code
> has many shortcomings:
> ~ inadequate topology discovery
> ~ fixed cpu set size
> ~ no clear separation of memory nodes
> ~ no inclusion of SMT/multicore in the cpu hierarchy
> ~ awkward (at best) memory allocation interface
> ~ etc etc
> and last but not least
> ~ a completely unacceptable library interface (e.g., global variables as
> part of the API, WTF?)
Regardless of issues addressed, Andi's been working with everyone for
something on the order of 12+ months and this is out of the blue. I very
very strongly suggest that you take up each of these issues with him so
that they can be addressed as individual incremental improvements to the
API everyone's been working with for all that time as opposed to screwing
the world (esp. now that commodity NUMA boxen are becoming more prevalent)
with transparent and deliberate distro-competition motivated API skew.
-- wli
next prev parent reply other threads:[~2004-04-30 8:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 7:35 NUMA API Ulrich Drepper
2004-04-30 8:30 ` William Lee Irwin III [this message]
2004-05-03 18:37 ` Ulrich Drepper
2004-05-04 10:01 ` Christoph Hellwig
2004-04-30 8:49 ` Paul Jackson
2004-04-30 9:50 ` William Lee Irwin III
2004-05-03 12:48 ` NUMA API - wish list Zoltan Menyhart
2004-05-03 17:57 ` Paul Jackson
[not found] <1QAMU-4gf-15@gated-at.bofh.it>
2004-04-30 20:01 ` NUMA API Andi Kleen
2004-05-01 5:15 ` Martin J. Bligh
2004-05-03 18:34 ` Ulrich Drepper
2004-04-30 20:39 ` Andi Kleen
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=20040430083017.GB1298@holomorphy.com \
--to=wli@holomorphy.com \
--cc=drepper@redhat.com \
--cc=linux-kernel@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