From: Nikita Danilov <Nikita@Namesys.COM>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>,
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 20:00:01 +0300 [thread overview]
Message-ID: <15957.2449.56807.954319@laputa.namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302201656030.30000-100000@localhost.localdomain>
Ingo Molnar writes:
>
[...]
>
> to fix this overhead i've introduced a 'lookup cursor' cookie, which is
> cached in filp->private_data, across readdir() [getdents64()] calls. If
> the cursor matches then we skip all the overhead of skipping threads. If
> the cursor is not available then we fall back to the old-style skipping
> algorithm.
Shouldn't filp->private_data be cleared on lseek? It looks like lookup
cursor is never cleared once set and so readdir will always go forward
independently of ->f_pos updates. Note that glibc implementation of
readdir() (on the top of getdents64()) does call lseek on the
directory. So does seekdir(3).
>
> 2) procps is forced to parse every thread in /proc to build up accurate
> 'process CPU usage' counters. The parsing and accessing of every
Nikita.
next prev parent reply other threads:[~2003-02-20 16:50 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 [this message]
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
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=15957.2449.56807.954319@laputa.namesys.com \
--to=nikita@namesys.com \
--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