mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Albert Cahalan <albert@users.sf.net>
Cc: Brian McGroarty <brian@mcgroarty.net>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	lm@bitmover.com
Subject: Re: /proc reliability & performance
Date: Thu, 16 Oct 2003 21:56:15 -0700	[thread overview]
Message-ID: <20031017045615.GB25291@holomorphy.com> (raw)
In-Reply-To: <1066365074.15931.195.camel@cube>

On Fri, Oct 17, 2003 at 12:31:14AM -0400, Albert Cahalan wrote:
> Count tasks as you read them. The number is
> your directory offset. Return a few dozen entries
> at a time. For each read, you'll need to find
> back your place. You do this by counting tasks
> until you reach your offset. Of course, tasks
> will have been created and destroyed between
> reads, so who knows where you'll continue from?
> That's simply not reliable.

That's part of what the rbtree algorithm was meant to address.
It does find_tgids_after(tgids, tgid_array), filling a buffer with the
tgids starting at the first one higher than its first argument. This
way there is no possibility whatsoever of duplicates or deviation from
sorted order.


-- wli

  reply	other threads:[~2003-10-17  4:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17  2:07 Albert Cahalan
2003-10-17  2:34 ` Larry McVoy
2003-10-17  8:01   ` dada1
2003-10-17  9:10     ` David S. Miller
2003-10-17 14:46       ` Valdis.Kletnieks
2003-10-17 17:24       ` dada1
2003-10-17 23:48       ` Albert Cahalan
2003-10-18  6:35       ` Willy Tarreau
2003-10-18  6:38         ` David S. Miller
2003-10-17  2:51 ` William Lee Irwin III
2003-10-17  3:24 ` Brian McGroarty
2003-10-17  4:31   ` Albert Cahalan
2003-10-17  4:56     ` William Lee Irwin III [this message]
2003-10-17  8:21     ` David Rees
2003-10-17  7:40 ` Zan Lynx
2003-10-17  7:54   ` William Lee Irwin III

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=20031017045615.GB25291@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=albert@users.sf.net \
    --cc=brian@mcgroarty.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.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

all inboxes | Powered by JetHome®