linux-numa.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Tordini <tordini@di.unito.it>
To: linux-numa@vger.kernel.org
Subject: libnuma - data types problems
Date: Mon, 07 Jan 2013 11:46:36 +0100	[thread overview]
Message-ID: <50EAA78C.3040307@di.unito.it> (raw)
In-Reply-To: <50EA9D7D.7090906@di.unito.it>

Hello,

I'm using libnuma for an enhanced NUMA-aware allocator. There are some 
functions which do not work as explained in the 'numa man page' or 
libnuma APIs. Precisely, I'm having problems with these functions: 
|numa_get_run_node_mask()| and |numa_node_to_cpus()|.

Concerning the former, reading the API and the manual, it returns a 
|struct bitmask *|, while the compiler asks for a |nodemask_t|.

The latter is supposed to require two parameters, as from API 
definition, but the compiler asks for three. If I pass three arguments 
as it asks - |(int node, unsigned long *buffer, int bufferlen) -| I get 
a /segfault/ every time, no matter the /bufferlen/ I use.

Maybe I'm doing something wrong, but I can't see what, since I'm 
trivially following APIs directives. I wonder whether there are some 
discrepancies between APIs and source code that have changed through 
libnuma versions. (btw, how do I check which libnuma/numactl is running 
on the machine? I working remotely on a server and |numactl| doesn't 
seem to have a |--version| option!)

Kind regards,

-- 

Fabio Tordini

PhD Candidate,
Computer Science Department
University of Torino - Italy


           reply	other threads:[~2013-01-07 10:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <50EA9D7D.7090906@di.unito.it>]

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=50EAA78C.3040307@di.unito.it \
    --to=tordini@di.unito.it \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).