From: Eric Dumazet <dada1@cosmosbay.com>
To: Zacco <zacco@fw.hu>
Cc: David Miller <davem@davemloft.net>,
baruch@ev-en.org, netdev@vger.kernel.org
Subject: Re: many sockets, slow sendto
Date: Thu, 22 Mar 2007 00:26:42 +0100 [thread overview]
Message-ID: <4601BF32.5070300@cosmosbay.com> (raw)
In-Reply-To: <4601A949.2000005@fw.hu>
Zacco a écrit :
> So, my worry is confirmed then. But how could that delay disappear when
> splitting the sender and receiver on distinct hosts? Even in that case
> the good socket must be found somehow.
When the receiver and sender are on the same machine, the sendto() pass the
packet to loopback and enters the receiving side. With that many sockets, the
time to go through all sockets maybe 100 us. So your sendto() seems to be
slow, but the slow part is the receiver.
If you put two machines, the sender might send XX.XXX frames per second (full
speed), but the receiver might handle 5% of them and drop 95%
This is all speculation, since you didnt gave us the exact setup you use.
next prev parent reply other threads:[~2007-03-21 23:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 15:08 many sockets, slow sendto Zaccomer Lajos
2007-03-06 18:20 ` Baruch Even
2007-03-19 23:10 ` Zacco
2007-03-19 23:16 ` David Miller
2007-03-20 21:59 ` Zacco
2007-03-20 22:48 ` Eric Dumazet
2007-03-21 21:53 ` Zacco
2007-03-21 22:24 ` Eric Dumazet
2007-03-21 23:26 ` Eric Dumazet [this message]
2007-03-22 1:14 ` David Miller
2007-03-21 22:12 ` Eric Dumazet
2007-03-22 1:15 ` David Miller
2007-03-22 6:43 ` Eric Dumazet
2007-03-29 19:24 ` Zacco
2007-03-30 13:10 ` Eric Dumazet
2007-04-22 12:34 ` Zacco
2007-04-30 7:26 ` David Miller
2007-04-30 10:56 ` YOSHIFUJI Hideaki / 吉藤英明
2007-04-30 12:47 ` Eric Dumazet
2007-04-30 19:43 ` YOSHIFUJI Hideaki / 吉藤英明
2007-04-30 19:59 ` Eric Dumazet
2007-03-06 19:23 ` Andi Kleen
2007-03-06 21:28 ` Zacco
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=4601BF32.5070300@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=baruch@ev-en.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=zacco@fw.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;
as well as URLs for NNTP newsgroup(s).