linux-kernel - Re: [rfc] "fair" rw spinlocks

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: <m1ocma1kz6.fsf@fess.ebiederm.org>
Date:	Mon, 07 Dec 2009 14:24:13 -0800
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	paulmck@...ux.vnet.ibm.com
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...e.hu>,
	Christoph Hellwig <hch@...radead.org>,
	Nick Piggin <npiggin@...e.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Oleg Nesterov <oleg@...hat.com>
Subject: Re: [rfc] "fair" rw spinlocks

"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> writes:
>
> Is it required that all of the processes see the signal before the
> corresponding interrupt handler returns?  (My guess is "no", which
> enables a trick or two, but thought I should ask.)

Not that I recall.  I think it is just an I/O completed signal.

>> The trouble as I recall is how to ensure new processes see the signal.
>
> And can we afford to serialize signals to groups of processes?  Not
> necessarily one at a time, but a limited set at a given time?
> Alternatively, a long list of pending group signals for each new task to
> walk?

Semantically I don't believe there are not any particular ordering
requirements, except that the work must be done before we return from
the kernel.

In the ideal implementation we could have hundreds of processes sending
signals to the same process group without affecting the rest of the
kernel.  The current implementation is a concern for scaling and we have
been removing it where we can.  

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