From: Andi Kleen <andi@firstfloor.org>
To: Elad Lahav <elahav@cs.uwaterloo.ca>
Cc: Andi Kleen <andi@firstfloor.org>,
Elad Lahav <elahav@uwaterloo.ca>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Implementation of the sendgroup() system call
Date: Mon, 4 May 2009 16:50:46 +0200 [thread overview]
Message-ID: <20090504145046.GI23223@one.firstfloor.org> (raw)
In-Reply-To: <20090504094431.174745mb0jhhm3s4@www.nexusmail.uwaterloo.ca>
On Mon, May 04, 2009 at 09:44:31AM -0400, Elad Lahav wrote:
> >My guess it's more the copies than the calls?
> It's a factor of both. This is why we also created the sendgroup()
> implementation that uses a tight loop of in-kernel calls to sendmsg()
> as a means for evaluating the cost of mode switches. It is definitely
> not negligible (exact numbers depend on the size of the group and the
> size of the payload, of course).
How much is non negligible in your case?
>
> >It sounds like you want sendfile() for UDP.
> Do you mean by having a per-recipient sendfile() call for the same
> file? Leaving the cost of the system call aside, this solution does
> not work well with the kind of real-time data that we've been working
> with (live streaming, online games). You would have to write the
> payload to the file as it is being generated and call sendfile() after
> each such write.
You can mmap the file.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-05-04 14:46 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 [this message]
2009-05-05 0:24 ` Elad Lahav
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=20090504145046.GI23223@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=elahav@cs.uwaterloo.ca \
--cc=elahav@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).