mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Gleb Natapov <gleb@minantech.com>
Cc: Hayim Shaul <hayim@post.tau.ac.il>, linux-kernel@vger.kernel.org
Subject: Re: mmap/munmap bug
Date: Tue, 22 Mar 2005 09:05:33 +0100	[thread overview]
Message-ID: <1111478733.7096.36.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20050322075658.GA32445@minantech.com>

On Tue, 2005-03-22 at 09:56 +0200, Gleb Natapov wrote:
> On Mon, Mar 21, 2005 at 07:34:02PM +0100, Arjan van de Ven wrote:
> > On Mon, 2005-03-21 at 17:32 +0200, Hayim Shaul wrote:
> > > Hi all,
> > > 
> > > I have an unexplained bug with mmap/munmap on 2.6.X.
> > > 
> > > I'm writing a kernel module that gives super-fast access to the network.
> > > It does so by doing mmap thus avoiding the memcpy to/from user.
> > 
> > well... you are aware the network stack already supports generic zero
> > copy networking, right ?
> > 
> 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.




  reply	other threads:[~2005-03-22  8:05 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 [this message]
2005-03-22  8:23       ` Hayim Shaul
2005-03-22  8:33         ` Arjan van de Ven
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=1111478733.7096.36.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®