netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bert hubert <bert.hubert@netherlabs.nl>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org
Subject: Re: nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz?
Date: Tue, 20 Feb 2007 09:04:58 +0100	[thread overview]
Message-ID: <20070220080457.GA20544@outpost.ds9a.nl> (raw)
In-Reply-To: <20070219155623.1d78785a@localhost.localdomain>

On Mon, Feb 19, 2007 at 03:56:23PM -0800, Stephen Hemminger wrote:

> > Linux 2.6.20-rc4 appears to take 4 microseconds on my P4 3GHz for a
> > non-blocking UDPv4 recvfrom() call, both on loopback and ethernet.
> > 
> > Linux 2.6.18 on my 64 bit Athlon64 3200+ takes a similar amount of time.

> > recvfrom itself is a tad worrisome, x=recvfrom. I didn't ask for the
> > 'libc_enable_asynccancel' stuff. I'm trying to isolate the actual syscall
> > but it is proving hard work for an assemnly newbie like me - socketcall
> > doesn't make things easier.

Together with Zwane Mwaikambo, we managed to isolate the pure syscall, it
doesn't make a difference, a single recvfrom continues to take around 4
microseconds at 3GHz. Many thanks to Zwane for helping out.

> Use oprofile to find the hotspot.

Will do this next - I need to get me a setup where I can do oprofile *and*
decent query rates, I don't do oprofile on my remote machines I don't have
easy access to.

Thanks.

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://netherlabs.nl              Open and Closed source services

  reply	other threads:[~2007-02-20  8:05 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 [this message]
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
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=20070220080457.GA20544@outpost.ds9a.nl \
    --to=bert.hubert@netherlabs.nl \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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).