All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cliff Wickman <cpw@sgi.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Bill Gray <bgray@redhat.com>, linux-numa@vger.kernel.org
Subject: Re: [PATCH] Rewrite numastat to also show per-node process stats
Date: Fri, 12 Oct 2012 11:49:03 -0500	[thread overview]
Message-ID: <20121012164903.GA15601@sgi.com> (raw)
In-Reply-To: <20121012154935.GD16230@one.firstfloor.org>

Hi Andi,

On Fri, Oct 12, 2012 at 05:49:35PM +0200, Andi Kleen wrote:
> On Wed, Oct 10, 2012 at 01:49:40PM -0500, Cliff Wickman wrote:
> > Hi Bill,
> > 
> > Thanks.  This numastat works fine in my tests.
> > It is included in numactl-2.0.8-rc6.tar.gz 
> > at ftp://oss.sgi.com/www/projects/libnuma/download/
> > 
> > To all on linux-numa:
> > 
> > This makes 22 patches since release 2.0.7 in April of 2011. 
> > It's way past due to release this as version 2.0.8.
> > 
> > I will do that very soon, unless any of you have found any reason not to. 
> 
> I'm not sure, did the IO affinity ever work on your SLES system?
> iirc there were still some issues.
> 
> -Andi

Yes, test/regress-io still fails for me.

> ./regress-io
testing ./node-parse file:.
libnuma: Warning: Cannot find block device 7:7 in sysfs for `.'
Failed to convert `file:.'
failed
testing ./node-parse ip:8.8.8.8
libnuma: Warning: Kernel does not know node mask for device
`/devices/pci0001:00/0001:00:04.0/'
Failed to convert `ip:8.8.8.8'
failed
...

I could use some help to fix that.  I haven't dug into it.
But IMO that shouldn't hold up all the other fixes that have been
accumulated in 2.0.8.

-- 
Cliff Wickman
SGI
cpw@sgi.com
(651) 683-3824

      reply	other threads:[~2012-10-12 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07  5:36 [PATCH] Rewrite numastat to also show per-node process stats Bill Gray
2012-10-10 18:49 ` Cliff Wickman
2012-10-12 15:49   ` Andi Kleen
2012-10-12 16:49     ` Cliff Wickman [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=20121012164903.GA15601@sgi.com \
    --to=cpw@sgi.com \
    --cc=andi@firstfloor.org \
    --cc=bgray@redhat.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.