From: Ulrich Drepper <drepper@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"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: Thu, 24 Sep 2009 14:07:03 -0700 [thread overview]
Message-ID: <4ABBDF77.3090106@redhat.com> (raw)
In-Reply-To: <4ABB767D.6080004@gmail.com>
-----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.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkq733cACgkQ2ijCOnn/RHQHzQCgsmre/xVEVghMVRWDCIevMPwc
+ecAmwaSOSLuSySZXRzSY/S64jf7K0Bd
=y6MN
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-09-24 21:07 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 ` Ulrich Drepper [this message]
2009-09-24 21:50 ` [PATCH] " Eric Dumazet
2009-09-26 15:01 ` Ingo Molnar
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=4ABBDF77.3090106@redhat.com \
--to=drepper@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=eric.dumazet@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
/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