[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201112021425.44897.pedro@codesourcery.com>
Date: Fri, 2 Dec 2011 14:25:44 +0000
From: Pedro Alves <pedro@...esourcery.com>
To: Pavel Emelyanov <xemul@...allels.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Cyrill Gorcunov <gorcunov@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Tejun Heo <tj@...nel.org>, Andrew Vagin <avagin@...nvz.org>,
Serge Hallyn <serge.hallyn@...onical.com>,
Vasiliy Kulikov <segoon@...nwall.com>
Subject: Re: [rfc 2/3] fs, proc: Introduce the Children: line in /proc/<pid>/status
On Friday 02 December 2011 14:17:08, Pavel Emelyanov wrote:
> O_O OK, I was wrong, they do live there. But I consider this as bug.
You can't change that. It'd break current gdb at least.
> Anyway -- my concern about unneeded memory overhead still stands.
> Even a simple find /proc will result in smth like
>
> /proc/1
> /proc/1/children/2
> /proc/1/children/2/children/4
> /proc/1/children/2/children/4
> /proc/1/children/3
> /proc/1/children/3/children/5
> /proc/2
> /proc/2/children/4
> /proc/3
> /proc/3/children/5
> /proc/4
> /proc/5
>
> Instead of
>
> /proc/1
> /proc/2
> /proc/3
> /proc/4
> /proc/5
>
> I.e. each task will be shown multiple times, which is not very fun, but memory exhaustive from my POV.
Now that is a good argument against hard linking. But not if you make
the entries under children/ symlinks. Then find doesn't recurse. And
then
$ find -L /proc/PID/
does recurse and give you the whole tree. Which I'd say is
actually useful...
--
Pedro Alves
--
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/
Powered by blists - more mailing lists