linux-kernel - Re: [RFC][PATCH 0/5] Signal scalability series

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: <20111004175235.GD3489@redhat.com>
Date:	Tue, 4 Oct 2011 19:52:35 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Matt Fleming <matt@...sole-pimps.org>,
	Tejun Heo <htejun@...il.com>, linux-kernel@...r.kernel.org,
	Tony Luck <tony.luck@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC][PATCH 0/5] Signal scalability series

On 10/04, Oleg Nesterov wrote:
>
> On 10/03, Peter Zijlstra wrote:
> >
> > Right, so the thing Thomas and I have been promoting for a while now is
> > to update a signal target vector on every signal mask update. Mask
> > updates should be the slow path. This would leave us with a ready target
> > in O(1).
>
> Yes. This is the "obvious" solution ;) Now that we have
> set_current_blocked() this is simple. Except, of course, this blows
> signal_struct and set_current_blocked() can't rely on TIF_SIGPENDING.
> But we can probably add TIF_YOU_ARE_LISTED_IN_CURR_TARGET_ARRAY.

Forgot to mention... Unblocking becomes "nontrivial" too. But almost
all these changes are local to set_current_blocked().

Oleg.

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