On 05/28/2014 10:28 PM, Vasily Kulikov wrote: > On Wed, May 28, 2014 at 16:44 +0400, Pavel Emelyanov wrote: >> On 05/28/2014 02:24 PM, Chen Hanxiao wrote: >>> We need a direct method of getting the pid inside containers. >> >> But there's more generic issue -- some day we'll need to know not only >> PIDs as seen from different namespaces, but also SIDs and PGIDs. > > Maybe include all per-ns ID in a separate file? This looks reasonable, but wouldn't this file be too big for a loaded system? > Then the old 'status' > file includes IDs from the current namespace only, the new file (e.g. > 'ids' or 'ns_ids') contains only hierarchical IDs which differ from > namespace to namespace for all possible namespaces. For all visible namespaces. I.e. -- if a task lives in a container and reads its /proc/self/status it should _not_ see its host pid. Just like it is now in the current patch. Otherwise it would bring blockers to live migration :( > It will be simplier > to parse the file -- if 'ns_ids' file contains some ID then this ID for > every ns can be obtained regardless of the specific ID name (SID, PID, > PGID, etc.). True, but given a task PID how to determine which pid namespaces it lives in to get the idea of how PIDs map to each other? Maybe we need some explicit API for converting (ID, NS1, NS2) into (ID)? Thanks, Pavel _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers
