From: Ingo Molnar <mingo@elte.hu>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Fr??d??ric Weisbecker <fweisbec@gmail.com>,
linux kernel <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf tools: Dont use openat()
Date: Sat, 26 Sep 2009 17:01:03 +0200 [thread overview]
Message-ID: <20090926150103.GB30071@elte.hu> (raw)
In-Reply-To: <4ABBE9B7.1050505@gmail.com>
* Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Ulrich Drepper a ??crit :
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Eric Dumazet wrote:
> >>> We can certainly remove that reliance - wanna send a patch for it?
> >
> > Come on, the silliness has to stop. The kernel must be recent and to
> > use it adequately the C library also must be recent. And "recent" is
> > not even correct anymore: the functions are available for more then two
> > years. Removing the use of the modern interfaces makes everything
> > slower and might even re-introduce race conditions my patch fixed.
> >
>
> First time I ear that C library *must* be recent. This was never
> mentionned in Documentation/Changes, "Minimal Requirements"
>
> "perf list" can be 100x slower, and even racy, I dont mind. At all.
>
> $ time perf list >/dev/null 2>/dev/null
>
> real 0m0.001s
> user 0m0.000s
> sys 0m0.001s
Yep, doesnt look problematic from a performance POV.
> With openat(), I cannot use "perf" on machines I can only change
> kernel, since changing glibc is too risky for legacy apps. I could use
> static and private glibc, but last time I tried this I lost few hours
> and failed.
Yeah, we generally dont want to force an upgrade of other components if
possible. The fact that you ran into it in a pre -rc1 kernel means that
there's a thousand others out there who will run into similar problems.
Ingo
next prev parent reply other threads:[~2009-09-26 15:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 13:05 [PATCH] perf tools: fix buffer allocation Eric Dumazet
2009-09-24 13:12 ` Ingo Molnar
2009-09-24 13:13 ` Eric Dumazet
2009-09-24 13:39 ` [PATCH] perf tools: Dont use openat() Eric Dumazet
2009-09-24 19:20 ` Ingo Molnar
2009-09-24 19:25 ` [tip:perf/urgent] " tip-bot for Eric Dumazet
2009-09-24 21:07 ` [PATCH] " Ulrich Drepper
2009-09-24 21:50 ` Eric Dumazet
2009-09-26 15:01 ` Ingo Molnar [this message]
2009-09-24 13:16 ` [tip:perf/urgent] perf tools: Fix buffer allocation tip-bot for Eric Dumazet
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=20090926150103.GB30071@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=drepper@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
/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®