From: Arjan van de Ven <arjan@infradead.org>
To: Hayim Shaul <hayim@post.tau.ac.il>
Cc: Gleb Natapov <gleb@minantech.com>, linux-kernel@vger.kernel.org
Subject: Re: mmap/munmap bug
Date: Tue, 22 Mar 2005 09:33:49 +0100 [thread overview]
Message-ID: <1111480429.7096.47.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0503221015500.10609@nova.cs.tau.ac.il>
On Tue, 2005-03-22 at 10:23 +0200, Hayim Shaul wrote:
> >> Does it support zero copy not only for send but also for receive? Can we
> >> receive packets directly to userspace buffers?
> >
> > that it can't currently, but without some major protocol stack rework
> > that's not going to be easy. If you want to help do that work,
> > excellent! Be sure to contact the people on net-dev mailinglist since
> > they are the ones having looked at this previously.
>
> My case is simpler, as the application I attend it to is similar to a NAT.
> A packet comes in, a little alternation of the headers and off it goes
> again. So there's no TCP-stack or anything.
>
> What I thought of doing, is map the skbuff to user-space. Have the
> user-application alter the headers. Send the (same) skbuff from
> kernel-space.
>
> Does there exist anything equivalent?
yes; netfilter has facilities for this actually afaik.
tcpdump also uses something like this (but only in one direction), it
mmaps some ringbuffer with incomming packets.
next prev parent reply other threads:[~2005-03-22 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 15:32 Hayim Shaul
2005-03-21 18:34 ` Arjan van de Ven
2005-03-22 7:56 ` Gleb Natapov
2005-03-22 8:05 ` Arjan van de Ven
2005-03-22 8:23 ` Hayim Shaul
2005-03-22 8:33 ` Arjan van de Ven [this message]
2005-03-22 9:44 ` Hayim Shaul
[not found] <20050322084545.88435.qmail@web15304.mail.bjs.yahoo.com>
2005-03-22 9:38 ` Hayim Shaul
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=1111480429.7096.47.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=gleb@minantech.com \
--cc=hayim@post.tau.ac.il \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®