All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: Damien Millescamps
	<damien.millescamps-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Get the socket id
Date: Wed, 7 Aug 2013 09:11:56 -0700	[thread overview]
Message-ID: <20130807091156.325e0cbc@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <52026E47.6090402-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>

On Wed, 07 Aug 2013 17:56:55 +0200
Damien Millescamps <damien.millescamps-pdR9zngts4EAvxtiuMwx3w@public.gmane.org> wrote:

> On 08/07/2013 05:52 PM, Stephen Hemminger wrote:
> > But can't find any documentation
> > on numa_maps in detail.
> You should try with man 5 numa_maps.
> 

Thanks, knew it was there some where:
       N<node>=<nr_pages>
              The number of pages allocated on  <node>.   <nr_pages>  includes
              only  pages currently mapped by the process.  Page migration and
              memory reclaim may have temporarily  unmapped  pages  associated
              with  this  memory  range.   These  pages may only show up again
              after the process has attempted to reference them.  If the  mem‐
              ory range represents a shared memory area or file mapping, other
              processes may currently have additional pages mapped in a corre‐
              sponding memory range.

      parent reply	other threads:[~2013-08-07 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07  6:14 Get the socket id dvr
     [not found] ` <77584a69.d001.1405769661d.Coremail.jinxiu.1006-9Onoh4P/yGk@public.gmane.org>
2013-08-07 15:52   ` Stephen Hemminger
     [not found]     ` <20130807085241.684ed79a-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2013-08-07 15:56       ` Damien Millescamps
     [not found]         ` <52026E47.6090402-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-08-07 16:11           ` Stephen Hemminger [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=20130807091156.325e0cbc@nehalam.linuxnetplumber.net \
    --to=stephen-otpzqlsittunbdjkjebofr2eb7je58tq@public.gmane.org \
    --cc=damien.millescamps-pdR9zngts4EAvxtiuMwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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.