All of lore.kernel.org
 help / color / mirror / Atom feed
From: "JaniD++" <djani22@dynamicweb.hu>
To: "Paul Jackson" <pj@sgi.com>
Cc: <linux-kernel@vger.kernel.org>, "Bill Davidsen" <davidsen@tmr.com>
Subject: Re: cpuset - question
Date: Tue, 1 Nov 2005 23:44:05 +0100	[thread overview]
Message-ID: <044801c5df35$c6ffc9c0$0400a8c0@dcccs> (raw)
In-Reply-To: 20051101142403.4b0897c9.pj@sgi.com

Thanks Paul Jackson, Bill Davidsen!

Yes, with echo 0 > mems, this is works fine! :-)

But the documentation is a little small for cpusets...

Thanks

Janos
----- Original Message ----- 
From: "Paul Jackson" <pj@sgi.com>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Tuesday, November 01, 2005 11:24 PM
Subject: Re: cpuset - question


> > In this config i need NUMA option enabled to use cpusets?
>
> No - if you got this far, cpusets are working for you.
>
> You would need NUMA if you had multiple memory nodes.
>
> I'm guessing you have one collection of RAM modules,
> all equally distant from the processors, which is not
> a NUMA (Non-Uniform-Memory-Architecture) system.
>
> I only mentioned NUMA because if you did have NUMA
> hardware, then you would need to CONFIG it into to
> your kernel to make full use of your multiple memory
> nodes.  I doubt that applies to you.
>
> It looks like you have multiple (4 logical with HT)
> CPUs, numbered 0, 1, 2, and 3, and one Memory Node,
> numbered 0.
>
> Cpusets should work for you - just "echo 0", not "echo 1"
> into the "mems" files.  Your one and only Memory Node
> is numbered "0", not "1".
>
> Actually, make that "/bin/echo", not "echo", so you can
> see the error messages.
>
> -- 
>                   I won't rest till it's the best ...
>                   Programmer, Linux Scalability
>                   Paul Jackson <pj@sgi.com> 1.925.600.0401
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2005-11-01 22:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 19:02 cpuset - question JaniD++
2005-11-01 20:36 ` Paul Jackson
2005-11-01 21:38   ` JaniD++
2005-11-01 22:24     ` Paul Jackson
2005-11-01 22:44       ` JaniD++ [this message]
2005-11-01 23:36         ` Paul Jackson
2005-11-01 21:52 ` Bill Davidsen
2005-11-01 22:26   ` Paul Jackson
  -- strict thread matches above, loose matches on Subject: below --
2005-11-02 10:36 Daniel J Blueman
2005-11-02 16:26 ` Randy.Dunlap
2005-11-02 17:35   ` Daniel J Blueman
2005-11-02 18:28     ` Paul Jackson
2005-11-02 18:48       ` Randy.Dunlap
2005-11-03  8:20       ` Simon Derr
2005-11-03  8:26     ` Sylvain Jeaugey

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='044801c5df35$c6ffc9c0$0400a8c0@dcccs' \
    --to=djani22@dynamicweb.hu \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.com \
    /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.