From: Elad Lahav <elad_lahav@users.sourceforge.net>
To: James Morris <jmorris@namei.org>
Cc: netdev@vger.kernel.org
Subject: Re: ip_append_page and the socket send buffer
Date: Fri, 16 Feb 2007 17:00:52 -0500 [thread overview]
Message-ID: <45D62994.6000609@users.sourceforge.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0702161627340.5602@d.namei>
James Morris wrote:
> On Fri, 16 Feb 2007, Elad Lahav wrote:
>
>> I wrote a function that is equivalent to udp_sendmsg, but uses ip_append_page
>> to attach data to an skb. The function is implemented as follows:
>
> Why?
This scheme allows you to send the same data to multiple recipients. The
user's data is copied only once into a set of pages, which are then
shared among multiple skbuff objects.
> Where is the code?
The code is probably too long to be attached to a mailing list message.
It pretty much follows the steps I specified in my original e-mail. I
can provide more details, if required.
Elad
prev parent reply other threads:[~2007-02-16 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 20:02 ip_append_page and the socket send buffer Elad Lahav
2007-02-16 21:27 ` James Morris
2007-02-16 22:00 ` Elad Lahav [this message]
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=45D62994.6000609@users.sourceforge.net \
--to=elad_lahav@users.sourceforge.net \
--cc=jmorris@namei.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).