linux-kernel - Re: [RFC] cpuset: add interface to isolated cpus

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061022234807.2000c888.pj@sgi.com>
Date:	Sun, 22 Oct 2006 23:48:07 -0700
From:	Paul Jackson <pj@....com>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	dino@...ibm.com, akpm@...l.org, mbligh@...gle.com,
	menage@...gle.com, Simon.Derr@...l.net,
	linux-kernel@...r.kernel.org, rohitseth@...gle.com, holt@....com,
	dipankar@...ibm.com, suresh.b.siddha@...el.com
Subject: Re: [RFC] cpuset: add interface to isolated cpus

> It would be trivial to make such a script to parse the root cpuset and
> do exactly this, wouldn't it?

Ah - yes - that's doable.  A certain company I work for ships pretty
much that exact script, to its customers.  It works well to remove
all the unpinned tasks from the top level cpuset and put them in what
we call the 'boot' cpuset, where the classic Unix load (init, cron,
daemons, sysadmin login) is confined.  This frees up the rest of the
system to run "real" work.  It works quite well, if I do say so.

Perhaps I'm being overly pessimistic about the potential of driving
this partitioning off the cpus_allowed masks of the tasks.  As you
noted, it would be a cute trick to avoid some combinatorial explosion
of the computational costs.  But there are enough practical constraints
on this problem - that should be quite doable.

Hmmm ...

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/