From: Thomas Gleixner <tglx@linutronix.de>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: Eric Dumazet <eric.dumazet@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: slow nanosleep?
Date: Wed, 8 Sep 2010 11:51:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1009081143200.2477@localhost6.localdomain6> (raw)
In-Reply-To: <OF2B75FA7C.7064BC41-ONC1257798.00318FDA-C1257798.00329AEF@transmode.se>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1403 bytes --]
On Wed, 8 Sep 2010, Joakim Tjernlund wrote:
> Eric Dumazet <eric.dumazet@gmail.com> wrote on 2010/09/08 10:24:49:
> >
> > Le mercredi 08 septembre 2010 à 10:04 +0200, Joakim Tjernlund a écrit :
> >
> > > That makes litte difference:
> > > root@localhost ~ # ./nanosleep
> > > nanosleep
> > > req:0 :0
> > > tv_res:0 :112
> > >
> >
> > Here, result is 30 (with prctl())
> > instead of 95 (without)
>
> On x86 I notice a difference:
> 7 vs 57.
> however select is still faster: 2
> The system call OH seems to be bigger for nanosleep than
> for select and on my ppc is is about 112 us. Can anything
> be done about that?
Hmm, the only reason I can see is that select calls finally
schedule_hrtimeout_range_clock() which optimizes the expiry = 0 case
while nanosleep does not. So the difference is only visiable when the
relative timeout is 0. For timeouts > 0 nanosleep and select should
behave the same way.
Thanks,
tglx
---
kernel/hrtimer.c | 3 +++
1 file changed, 3 insertions(+)
Index: linux-2.6/kernel/hrtimer.c
===================================================================
--- linux-2.6.orig/kernel/hrtimer.c
+++ linux-2.6/kernel/hrtimer.c
@@ -1609,6 +1609,9 @@ SYSCALL_DEFINE2(nanosleep, struct timesp
if (!timespec_valid(&tu))
return -EINVAL;
+ if (!tu.tv_sec && !tu.tv_usec)
+ return 0;
+
return hrtimer_nanosleep(&tu, rmtp, HRTIMER_MODE_REL, CLOCK_MONOTONIC);
}
next prev parent reply other threads:[~2010-09-08 9:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 7:45 Joakim Tjernlund
2010-09-08 7:56 ` Eric Dumazet
2010-09-08 8:04 ` Joakim Tjernlund
2010-09-08 8:24 ` Eric Dumazet
2010-09-08 9:12 ` Joakim Tjernlund
2010-09-08 9:51 ` Thomas Gleixner [this message]
2010-09-08 10:14 ` Eric Dumazet
2010-09-08 10:17 ` Thomas Gleixner
2010-09-08 12:11 ` Joakim Tjernlund
2010-09-08 12:43 ` Thomas Gleixner
2010-09-08 13:00 ` Peter Zijlstra
2010-09-08 13:44 ` Joakim Tjernlund
2010-09-08 13:51 ` Peter Zijlstra
2010-09-08 13:52 ` Thomas Gleixner
2010-09-08 14:19 ` Joakim Tjernlund
2010-09-08 14:30 ` Thomas Gleixner
2010-09-08 14:33 ` Joakim Tjernlund
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=alpine.LFD.2.00.1009081143200.2477@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=eric.dumazet@gmail.com \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-kernel@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®