linux-kernel - Re: [PATCH 00/10] Scalability requirements for sysv ipc

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]

Date:	Tue, 29 Apr 2008 11:54:24 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Nadia.Derbey@...l.net
Cc:	manfred@...orfullife.com, paulmck@...ux.vnet.ibm.com,
	linux-kernel@...r.kernel.org, efault@....de
Subject: Re: [PATCH 00/10] Scalability requirements for sysv ipc - v2

On Tue, 29 Apr 2008 16:33:04 +0200
Nadia.Derbey@...l.net wrote:

> After scalability problems had been detected when using the sysV ipcs, I
> have proposed to use an RCU based implementation of the IDR api instead
> (see thread http://lkml.org/lkml/2008/4/11/212).
> 
> Resending the patch series after
>  . integrating Paul's remarks
>  . fixing a bug I had introduced
>  . porting it to 2.6.25-mm1.
> 
> Reviewers are still welcome!
> 
> Patch 1 can be taken alone: it fixes a problem in the existing IDR API.
> 
> Patches should be applied on linux-2.6.25-mm1, in the following order:
> 
> [ PATCH 01/10 ] : idr_minor_fix.patch
> [ PATCH 02/10 ] : ridr_structure.patch
> [ PATCH 03/10 ] : ridr_pre_get.patch
> [ PATCH 04/10 ] : ridr_init.patch
> [ PATCH 05/10 ] : ridr_get_new_above.patch
> [ PATCH 06/10 ] : ridr_get_new.patch
> [ PATCH 07/10 ] : ridr_find.patch
> [ PATCH 08/10 ] : ridr_remove.patch
> [ PATCH 09/10 ] : ipc_use_ridr.patch
> [ PATCH 10/10 ] : remove_ipc_lock_down.patch
> 

hm, you've been busy.

As all this work is entirely for performance reasons, the changelog should
have (lots of) performance testing results!  Please.


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