netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: bert hubert <bert.hubert@netherlabs.nl>
Cc: Benjamin LaHaise <bcrl@kvack.org>,
	Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
	Josef Sipek <jsipek@fsl.cs.sunysb.edu>,
	Andi Kleen <andi@firstfloor.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: all syscalls initially taking 4usec on a P4? Re: nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz?
Date: Tue, 20 Feb 2007 13:02:26 -0800	[thread overview]
Message-ID: <20070220130226.7fb80d20@freekitty> (raw)
In-Reply-To: <20070220204505.GB8800@outpost.ds9a.nl>

On Tue, 20 Feb 2007 21:45:05 +0100
bert hubert <bert.hubert@netherlabs.nl> wrote:

> On Tue, Feb 20, 2007 at 02:40:40PM -0500, Benjamin LaHaise wrote:
> 
> > Make sure your system is idle.  Userspace bloat means that *lots* of idle 
> > activity occurs in between timer ticks on recent distributions -- all those 
> 
> You hit the nail on the head. I had previously measured with X shut down,
> but the effect didn't disappear.
> 
> With init=/bin/bash, recvfrom suddenly takes from 900nsec to 1.3usec, with
> only slight correlation between inter-call delay and cycles spent.
> 
> I'm investigating this further as it appears this has a real life effect on
> my P4 - a drastic one!
> 
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 15
> model           : 4
> model name      : Intel(R) Pentium(R) 4 CPU 3.00GHz
> stepping        : 1
> cpu MHz         : 3000.131
> cache size      : 1024 KB
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 5
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx
> constant_tsc pni monitor ds_cpl cid xtpr
> bogomips        : 6003.91
> clflush size    : 64
> 
> Thanks for your help!
> 

What happens with preempt if your process is high priority or SCHED_FIFO/SCHED_RR?

-- 
Stephen Hemminger <shemminger@linux-foundation.org>

  reply	other threads:[~2007-02-20 21:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19 23:14 nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz? bert hubert
2007-02-19 23:56 ` Stephen Hemminger
2007-02-20  8:04   ` bert hubert
2007-02-20 10:50 ` Andi Kleen
2007-02-20 16:27   ` all syscalls initially taking 4usec on a P4? " bert hubert
2007-02-20 16:41     ` Evgeniy Polyakov
2007-02-20 17:02       ` bert hubert
2007-02-20 17:11         ` Evgeniy Polyakov
2007-02-20 17:18           ` Evgeniy Polyakov
2007-02-21 11:06           ` Evgeniy Polyakov
2007-02-21 11:34             ` Andi Kleen
2007-02-20 18:42       ` Josef Sipek
2007-02-20 18:48         ` Evgeniy Polyakov
2007-02-20 19:33           ` bert hubert
2007-02-20 19:40             ` Benjamin LaHaise
2007-02-20 20:45               ` bert hubert
2007-02-20 21:02                 ` Stephen Hemminger [this message]
2007-02-20 22:02             ` Rick Jones
2007-02-20 22:17               ` bert hubert
2007-02-20 22:22                 ` Arjan van de Ven
2007-02-21 16:25                   ` Chuck Ebbert
2007-02-20 22:46                 ` Ian McDonald
2007-02-25 10:41       ` Pavel Machek
2007-02-25 17:06         ` Evgeniy Polyakov
2007-02-20 16:57     ` 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=20070220130226.7fb80d20@freekitty \
    --to=shemminger@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=bcrl@kvack.org \
    --cc=bert.hubert@netherlabs.nl \
    --cc=johnpol@2ka.mipt.ru \
    --cc=jsipek@fsl.cs.sunysb.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).