From: Petr Holasek <pholasek@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Cliff Wickman <cpw@sgi.com>,
linux-numa@vger.kernel.org, Anton Arapov <anton@redhat.com>
Subject: Re: [RFC PATCH 4/7] libnuma: introduced _all versions of numa_parse_{cpu,node}string()
Date: Fri, 17 Aug 2012 16:17:43 +0200 [thread overview]
Message-ID: <20120817141742.GA13886@machinehead.brq.redhat.com> (raw)
In-Reply-To: <20120816160035.GJ11413@one.firstfloor.org>
On Thu, 16 Aug 2012, Andi Kleen wrote:
> On Thu, Aug 16, 2012 at 05:16:33PM +0200, Petr Holasek wrote:
> > This patch adds new interfaces numa_parse_cpustring_all() and
> > numa_parse_nodestring_all(). The functions are able to parse
> > input string to bitmask regardless current task's cpuset or
> > available nodes.
>
> If you add new functions you need to give them a new symbol version
> (1.3). You cannot just add them to the old fixed ABI.
>
Ah, thanks. I'll do it.
Regards,
Petr H
next prev parent reply other threads:[~2012-08-17 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 15:16 [PATCH 0/7] couple of numactl-2.0.8-rc4 bugfixes and interface Petr Holasek
2012-08-16 15:16 ` [PATCH 1/7] libnuma: Fix calculation of maxconfiguredcpu Petr Holasek
2012-08-16 15:16 ` [PATCH 2/7] libnuma: do not recalculate maxconfiguredcpu Petr Holasek
2012-08-16 15:16 ` [PATCH 3/7] libnuma: numa_num_possible_cpus symbol is exported from the library Petr Holasek
2012-08-16 15:16 ` [RFC PATCH 4/7] libnuma: introduced _all versions of numa_parse_{cpu,node}string() Petr Holasek
2012-08-16 16:00 ` Andi Kleen
2012-08-17 14:17 ` Petr Holasek [this message]
2012-08-16 15:16 ` [PATCH 5/7] libnuma: numa_parse_cpustring and similar should take a const char* parameter Petr Holasek
2012-08-16 15:16 ` [PATCH 6/7] libnuma: removed unused bufferlen variable Petr Holasek
2012-08-16 15:16 ` [PATCH 7/7] libnuma: no warnings when there are holes in numbering of nodes Petr Holasek
2012-08-27 12:20 ` [PATCH 0/7] couple of numactl-2.0.8-rc4 bugfixes and interface Cliff Wickman
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=20120817141742.GA13886@machinehead.brq.redhat.com \
--to=pholasek@redhat.com \
--cc=andi@firstfloor.org \
--cc=anton@redhat.com \
--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 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.