From: Andrew Grover <andy.grover@gmail.com>
To: Tom Herbert <therbert@google.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: Generalizing mmap'ed sockets
Date: Fri, 19 Nov 2010 14:10:05 -0800 [thread overview]
Message-ID: <AANLkTim+HaoTr_MdgFmWM3OeRttsAMsF1d++vm8gTo+N@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=WF2hAGAufv_Anc=b=Fm2WOpOMOv1UrDRvaTHp@mail.gmail.com>
On Fri, Nov 19, 2010 at 12:04 PM, Tom Herbert <therbert@google.com> wrote:
> This is a project I'm contemplating. If you have any comments or can
> point me to prior work in this area that would be appreciated.
> TX:
> - Zero copy transmit (which is already supported by vmsplice(), but
> this might be simpler)
> - One system call needed on transmit which can cover multiple
> datagrams or what would have been multiple writes (the call is just to
> kick kernel to start sending)
I'd look at our existing recvmmsg syscall -- there was talk of doing a
sendmmsg, which sounds close to what you want.
> RX:
> - Zero system calls needed to do receive (determining data ready is
> accomplished by polling)
> - Immediate data placement in kernel available all the time,
> including OOO placement
> - Potential for true zero copy on receive with device support (like
> per flow queues, UDP queues)
Mentioning zero-copy per-flow queues in userspace suggests Infiniband
is prior work in this area.
Regards -- Andy
prev parent reply other threads:[~2010-11-19 22:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 20:04 Generalizing mmap'ed sockets Tom Herbert
2010-11-19 21:32 ` Rick Jones
2010-11-19 21:52 ` David Miller
2010-11-19 21:55 ` Tom Herbert
2010-11-19 21:58 ` Rick Jones
2010-11-19 22:08 ` David Miller
2010-11-19 22:47 ` Rick Jones
2010-11-19 22:49 ` Tom Herbert
2010-11-24 19:57 ` Michael S. Tsirkin
2010-11-19 22:10 ` Andrew Grover [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=AANLkTim+HaoTr_MdgFmWM3OeRttsAMsF1d++vm8gTo+N@mail.gmail.com \
--to=andy.grover@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
/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).