public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: davidm@hpl.hp.com
Cc: drepper@redhat.com, libc-hacker@sources.redhat.com
Subject: Re: enabling caching for dl_iterate_phdr()
Date: Tue, 23 Dec 2003 22:24:00 -0000	[thread overview]
Message-ID: <200312232224.hBNMON0p029115@magilla.sf.frob.com> (raw)
In-Reply-To: David Mosberger's message of  Tuesday, 16 December 2003 11:54:57 -0800 <200312161954.hBGJsvaC003146@napali.hpl.hp.com>

> Would it be possible to add two atomic counters, dl_load_additions and
> dl_load_removals, which would get incremented whenever something is a
> phdr is added to/removed from the list that is traversed by
> dl_iterate_phdr()?

What interface do you propose for exposing such counters?
We won't be adding any published interfaces using variables.

> Any opinions?  I guess the alternative that was mentioned in the past
> was to use callbacks, but that seems very dangerous in regards to
> deadlock etc.

If your callback functions do nothing but increment atomic counters of your
own, then there is no problem.

  reply	other threads:[~2003-12-23 22:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-16 19:55 David Mosberger
2003-12-23 22:24 ` Roland McGrath [this message]
     [not found] <16387.9755.753294.37588@napali.hpl.hp.com>
2004-01-17  0:57 ` Roland McGrath
2004-01-17  1:39   ` Jakub Jelinek
2004-01-17  1:40     ` Roland McGrath
2004-01-17  1:51     ` David Mosberger
2004-01-22  0:35     ` David Mosberger
2004-01-22  8:39       ` Jakub Jelinek
2004-01-24  5:54         ` David Mosberger
2004-01-24 20:27           ` Ulrich Drepper
2004-01-26 21:48             ` David Mosberger
2004-01-26 22:39               ` Ulrich Drepper
2004-01-26 22:58                 ` Roland McGrath
2004-01-26 23:03                 ` David Mosberger

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=200312232224.hBNMON0p029115@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).