public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Weigle <ehw@lanl.gov>
To: Lars Brinkhoff <lars.spam@nocrew.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Magic Lantern
Date: Wed, 28 Nov 2001 12:33:41 -0700	[thread overview]
Message-ID: <20011128123341.K22767@lanl.gov> (raw)
In-Reply-To: <Pine.LNX.3.95.1011128090654.10732B-100000@chaos.analogic.com> <20011128081305.I22767@lanl.gov> <85oflmvi8g.fsf@junk.nocrew.org>
In-Reply-To: <85oflmvi8g.fsf@junk.nocrew.org>

On Wed, Nov 28, 2001 at 07:54:39PM +0100, Lars Brinkhoff wrote:
> Eric Weigle <ehw@lanl.gov> writes:
> > > > "Richard B. Johnson" <root@chaos.analogic.com> writes:
> > > > > Basically, a "tee" to capture all network packets and pass them
> > > > > on to a filtering task without affecting normal network activity.
> > > > The af_packet module can read and write raw ethernet frames.
> > The af_packet module may also be fairly inefficient. If you need
> > performance over, say, a gigabit link, you may have trouble.
> 
> Are you (or anyone else) aware of any alternative?
I'm sure it's just something silly that's hurt the performance of the
af_packet module (perhaps already fixed, perhaps in my methodology :|)

For the purposes of the work I was doing here (totally unrelated to this
Magic Lantern BS, which I didn't even know what it was until after I posted
the first response in this thread), I just needed to saturate a gigE link for
testing. To do this I just used three boxes flooding UDP packets and that
worked. As far as traffic collection goes (which is what I was testing),
we went with another approach-- an optical tap to snarf off a copy of all
the data on a link, and then a custom kernel I hacked up to do the work
in the kernel itself (avoiding the kernel--user space copy and the stack
entirely). This is not for the faint of heart.


-Eric

-- 
--------------------------------------------
 Eric H. Weigle   CCS-1, RADIANT team
 ehw@lanl.gov     Los Alamos National Lab
 (505) 665-4937   http://home.lanl.gov/ehw/
--------------------------------------------

      reply	other threads:[~2001-11-28 19:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28 13:36 Magic Lantern Richard B. Johnson
2001-11-28 13:41 ` David S. Miller
2001-11-28 13:56 ` Lars Brinkhoff
2001-11-28 14:07   ` Richard B. Johnson
2001-11-28 15:13     ` Eric Weigle
2001-11-28 15:48       ` Richard B. Johnson
2001-11-28 18:54       ` Lars Brinkhoff
2001-11-28 19:33         ` Eric Weigle [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=20011128123341.K22767@lanl.gov \
    --to=ehw@lanl.gov \
    --cc=lars.spam@nocrew.org \
    --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