Scalability requirements for sysv ipc - v2
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest10 patches 15 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/10 | Fix idr_remove()lib/ | +1 | 2 replies | |
| 2/10 | Introduce the ridr structureinclude/ include/ init/ +3 more | +83 | 1 reply | |
| 3/10 | Introduce ridr_pre_get()include/ lib/ | +47 | 1 reply | |
| 4/10 | Introduce ridr_init()include/ lib/ | +15 | 1 reply | |
| 5/10 | Introduce ridr_get_new_above()include/ include/ lib/ +1 more | +287 | 2 replies | |
| 6/10 | Introduce ridr_get_new()include/ lib/ | +28 | 1 reply | |
| 7/10 | Introduce ridr_find()include/ lib/ | +51 | 1 reply | |
| 8/10 | Introduce ridr_remove()include/ include/ lib/ +1 more | +89 | 1 reply | |
| 9/10 | Integrate the ridr code into IPC codeinclude/ ipc/ ipc/ +1 more | +20 | 1 reply | |
| 10/10 | Get rid of ipc_lock_down()ipc/ ipc/ ipc/ | +4 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 00/10] Scalability requirements for sysv ipc - v2
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
Regards,
Nadia
--