mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: mohan kumar <mohan_linux@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: lug@lug.boulder.co.us
Subject: kernel to user space transactions
Date: Fri, 11 May 2001 10:02:44 -0700 (PDT)	[thread overview]
Message-ID: <20010511170244.71793.qmail@web13405.mail.yahoo.com> (raw)

hi,
we are developing a protocol analyser. our application
needs to capture 100 mbps full duplex traffic. we have
the application in windows which does the same. we are
now trying to port it to linux. we came up with a
basic application that captures traffic. iam very
happy to say that linux was able to capture 100 mbps
full duplex traffic more ( a lot of mores :-) to be
correct) efficiantly than windows. now that we are
ready to port the application to linux, we are trying
to find the best way to transfer data to the user
space from kernel space. we tried normal blocking read
and it works fine. but we dont want to waste cycle on
transfering data to and fro kernel and user land. so
we tried some other techniques like remaping the
kernel land buffers to userland via mmap. that also
works fine. 

now we have a doubt that, like maping kernal space
buffers to user space, weather we will be able to map
user space buffers to kernel space(so that we can
write data directly from packet capture
function(registered via dev_add_pack))

so can u guys point out weather that kind of approach
will work and if so where do i start looking?.

thanx,
Mohan Kumar S
Amoeba Telecom
(visit us at www.amoebatel.com)



__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/

                 reply	other threads:[~2001-05-11 17:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010511170244.71793.qmail@web13405.mail.yahoo.com \
    --to=mohan_linux@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lug@lug.boulder.co.us \
    /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®