[trying to reconstruct cc list, since the cc: field is bust again] > On Fri, 19 Nov 2021 11:47:36 -0500 > Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > > > Can we back up and ask what problem you're trying to solve before > > > we start introducing new objects like namespace name? > > TL;DR; verison: > > We want to be able to install a container on a machine that will let > us view all namespaces currently defined on that machine and which > tasks are associated with them. > > That's basically it. So you mentioned kubernetes. Have you tried kubectl get pods --all-namespaces ? The point is that orchestration systems usually have interfaces to get this information, even if the kernel doesn't. In fact, userspace is almost certainly the best place to construct this from. To look at this another way, what if you were simply proposing the exact same thing but for the process tree. The push back would be that we can get that all in userspace and there's even a nice tool (pstree) to do it which simply walks the /proc interface. Why, then, do we have to do nstree in the kernel when we can get all the information in exactly the same way (walking the process tree)? James
