RFC Introduce task_pid api
Get series with b4
b4 am 20051114212341.724084000@sergelapVersions newest first
- v1 RFC Latest13 patches 70 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/13 | Change pid accesses: driversdrivers/ drivers/ drivers/ +43 more | +94 | 0 replies | |
| 2/13 | Change pid accesses: most archsarch/ arch/ arch/ +102 more | +194 | 0 replies | |
| 3/13 | Change pid accesses: filesystems.fs/ fs/ fs/ +40 more | +86 | 0 replies | |
| 4/13 | Change pid accesses: include/.include/ include/ | +2 | 0 replies | |
| 5/13 | Change pid accesses: ipcipc/ ipc/ ipc/ +1 more | +14 | 0 replies | |
| 6/13 | Change pid accesses: kernel/kernel/ kernel/ kernel/ +16 more | +89 | 0 replies | |
| 7/13 | Change pid accesses: lib/lib/ lib/ lib/ +1 more | +9 | 0 replies | |
| 8/13 | Change pid accesses: mm/mm/ mm/ | +12 | 0 replies | |
| 9/13 | Change pid accesses: net/net/ net/ net/ +13 more | +24 | 0 replies | |
| 10/13 | Change pid accesses: security/security/ security/ security/ +2 more | +15 | 0 replies | |
| 11/13 | Change pid accesses: sound/sound/ sound/ sound/ +6 more | +15 | 0 replies | |
| 12/13 | Change pid accesses: ia64 and mipsarch/ arch/ arch/ +20 more | +200 | 3 replies | |
| 13/13 | Define new task_pid apiinclude/ | +13 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC] [PATCH 00/13] Introduce task_pid api
--
I'm part of a project implementing checkpoint/restart processes. After a process or group of processes is checkpointed, killed, and restarted, the changing of pids could confuse them. There are many other such issues, but we wanted to start with pids.
This patchset introduces functions to access task->pid and ->tgid, and updates ->pid accessors to use the functions. This is in preparation for a subsequent patchset which will separate the kernel and virtualized pidspaces. This will allow us to virtualize pids from users' pov, so that, for instance, a checkpointed set of processes could be restarted with particular pids. Even though their kernel pids may already be in use by new processes, the checkpointed processes can be started in a new user pidspace with their old virtual pid. This also gives vserver a simpler way to fake vserver init processes as pid 1. Note that this does not change the kernel's internal idea of pids, only what users see.
The first 12 patches change all locations which access ->pid and ->tgid to use the inlined functions. The last patch actually introduces task_pid() and task_tgid(), and renames ->pid and ->tgid to __pid and __tgid to make sure any uncaught users error out.
Does something like this, presumably after much working over, seem mergeable?
thanks
-serge