From: Daniel Jacobowitz <dan@debian.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Alex Larsson <alexl@redhat.com>,
procps-list@redhat.com
Subject: Re: [patch] procfs/procps threading performance speedup, 2.5.62
Date: Thu, 20 Feb 2003 14:13:58 -0500 [thread overview]
Message-ID: <20030220191358.GA18459@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0302200918300.2493-100000@home.transmeta.com>
On Thu, Feb 20, 2003 at 09:20:38AM -0800, Linus Torvalds wrote:
>
> On Thu, 20 Feb 2003, Linus Torvalds wrote:
> >
> > It would just be _so_ much nicer if the threads would show up as
> > subdirectories ie /proc/<tgid>/<tid>/xxx. More scalable, more readable,
> > and just generally more sane.
>
> It shouldn't even be all that much harder. You only really need to add the
> "lookup()" and "readdir()" logic to the pid-fd's, and they both should be
> fairly straightforward, ie something like the appended should do the
> lookup() part.
>
> (UNTESTED! NOT COMPILED! PROBABLY HORRIBLY BUGGY! CAVEAT USER! CONCEPTUAL
> CODE ONLY! YOU GET THE IDEA! I'M GETTING HOARSE FROM ALL THE SHOUTING!)
It'd be a little (very little) more complex, but can I once again
suggest /proc/<tgid>/threads/<tid> instead of /proc/<tgid>/<tid>/xxx?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-02-20 19:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 16:33 [patch] procfs/procps threading performance speedup, 2.5.62 Ingo Molnar
2003-02-20 16:47 ` Miquel van Smoorenburg
2003-02-20 16:55 ` Daniel Jacobowitz
2003-02-20 17:00 ` Nikita Danilov
2003-02-20 17:06 ` Linus Torvalds
2003-02-20 17:14 ` Ingo Molnar
2003-02-20 17:22 ` Linus Torvalds
2003-02-21 7:38 ` Oliver Xymoron
2003-02-20 17:23 ` Ingo Molnar
2003-02-22 20:52 ` Albert Cahalan
2003-02-22 21:55 ` Andrew Morton
2003-02-22 23:04 ` Albert Cahalan
2003-02-23 18:49 ` Ingo Molnar
2003-02-23 21:51 ` Albert D. Cahalan
2003-02-24 9:28 ` Ingo Molnar
2003-02-24 11:12 ` Albert D. Cahalan
2003-02-24 11:26 ` Ingo Molnar
2003-02-24 12:29 ` Albert D. Cahalan
2003-02-24 12:41 ` Ingo Molnar
2003-02-24 12:45 ` Ingo Molnar
2003-02-24 12:52 ` Ingo Molnar
2003-02-24 9:38 ` Ingo Molnar
2003-02-24 12:13 ` Albert D. Cahalan
2003-02-20 17:28 ` Jeff Garzik
2003-02-20 17:30 ` Ingo Molnar
2003-02-20 17:48 ` Linus Torvalds
2003-02-20 17:20 ` Linus Torvalds
2003-02-20 19:13 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030220191358.GA18459@nevyn.them.org \
--to=dan@debian.org \
--cc=alexl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=procps-list@redhat.com \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox