From: Elad Lahav <elahav@uwaterloo.ca>
To: Andi Kleen <andi@firstfloor.org>
Cc: Elad Lahav <elahav@cs.uwaterloo.ca>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Implementation of the sendgroup() system call
Date: Mon, 04 May 2009 20:24:35 -0400 [thread overview]
Message-ID: <49FF8743.1090704@uwaterloo.ca> (raw)
In-Reply-To: <20090504145046.GI23223@one.firstfloor.org>
> How much is non negligible in your case?
Please see the following link
http://www.cs.uwaterloo.ca/~elahav/sendgroup/mb_pkt_size.pdf
for a graph showing the (amortised) cost of sending a single packet to a
group of 1000 recipients, using one of the three following methods:
1. A user-mode loop of sendmsg() calls
2. A kernel-mode loop of udp_sendmsg() calls
3. A single call to sendgroup()
The cost is measured in cycles and was determined using performance
counters.
In this benchmark, savings introduced by sendgroup() are primarily due
to the aviodence of multiple system calls, up to a packet size of about
1000 bytes. Obviously, proportions change for different group sizes
(though we were able to outperform method 1 with a group size as small
as 2).
--Elad
next prev parent reply other threads:[~2009-05-05 0:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49FE47A1.7070700@uwaterloo.ca>
2009-05-04 7:13 ` [PATCH] Implementation of the sendgroup() system call Andi Kleen
2009-05-04 7:30 ` Avi Kivity
2009-05-04 9:53 ` Andi Kleen
2009-05-04 9:56 ` Eric Dumazet
2009-05-04 10:18 ` Andi Kleen
2009-05-04 9:58 ` Avi Kivity
2009-05-04 7:42 ` Rémi Denis-Courmont
2009-05-04 13:44 ` Elad Lahav
2009-05-04 14:50 ` Andi Kleen
2009-05-05 0:24 ` Elad Lahav [this message]
2009-05-06 11:25 ` Tim Brecht
[not found] ` <49FE9C8C.6090705@cosmosbay.com>
2009-05-04 9:03 ` 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=49FF8743.1090704@uwaterloo.ca \
--to=elahav@uwaterloo.ca \
--cc=andi@firstfloor.org \
--cc=elahav@cs.uwaterloo.ca \
--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).