linux-kernel - Re: [PATCH] cpuset: Make rebuild_sched

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: <6599ad830807150911jede167ewbcdfdff905b5059e@mail.gmail.com>
Date:	Tue, 15 Jul 2008 09:11:10 -0700
From:	"Paul Menage" <menage@...gle.com>
To:	"Paul Jackson" <pj@....com>
Cc:	"Max Krasnyansky" <maxk@...lcomm.com>, mingo@...e.hu,
	linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl
Subject: Re: [PATCH] cpuset: Make rebuild_sched_domains() usable from any context

On Tue, Jul 15, 2008 at 9:07 AM, Paul Jackson <pj@....com> wrote:
> If this rebuild thread was the -only- way that sched domains were
> allowed to be rebuilt, and if this rebuild was done -asynchronously-
> sometime shortly after requested, without any error or status feedback,
> then it would seem to simplify the locking issues.

I sent a patch that was similar a couple of weeks ago, that used a
workqueue to do the rebuild. It didn't quite work then since it wasn't
safe to call get_online_cpus() from a multi-threaded workqueue then,
but I believe there's been a patch since then that makes this safe.
And if not, we could always have a single-threaded workqueue that
wasn't bound to any particular CPU.

Paul
--
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/