From: Mark Smith <lk-netdev@lk-netdev.nosense.org>
To: Luca Deri <deri@ntop.org>
Cc: David Miller <davem@davemloft.net>,
bcook@bpointsys.com, brad.doctor@gmail.com,
netdev@vger.kernel.org
Subject: Re: PF_RING: Include in main line kernel?
Date: Thu, 15 Oct 2009 07:20:41 +1030 [thread overview]
Message-ID: <20091015072041.6ebae736@opy.nosense.org> (raw)
In-Reply-To: <C803B824-8249-44BA-ACCD-D9AE4AA21F92@ntop.org>
Hi Luca, David,
On Wed, 14 Oct 2009 22:34:17 +0200
Luca Deri <deri@ntop.org> wrote:
> David
> so do you want me to start porting PF_RING facilities into PF_PACKET?
> As I have said I;m not against this: my goal is to include this work
> into the linux kernel, as it has been separate for too long.
>
I'd like to see that. One of my main uses for Linux is as a network
troubleshooting "pocket knife", so anything that can improve or make
more functional the packet capturing capabilities is really appreciated
by people like me.
Thanks,
Mark.
> Luca
>
> On Oct 14, 2009, at 10:29 PM, David Miller wrote:
>
> > From: Luca Deri <deri@ntop.org>
> > Date: Wed, 14 Oct 2009 22:26:25 +0200
> >
> >> I agree that some PF_RING features could be merged into
> >> PF_PACKET. However PF_RING is not just about improving packet capture
> >> but it implements facilities that can be used by many monitoring
> >> applications including, packet balancing, reflection, layer-7 packet
> >> filtering, pf_ring socket clustering just to name a few. You can read
> >> about PF_RING feature into this tutorial:
> >> http://luca.ntop.org/IM2009_Tutorial.pdf
> >
> > I've already researched several times what PF_RING does and
> > is capable of doing, and my position still stands that none of
> > it can't be added to existing facilities.
> >
> > It's been an out of tree hack for years, and if it stays as
> > a seperate facility it's likely to stay that way.
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-14 20:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 14:33 PF_RING: Include in main line kernel? Brad Doctor
2009-10-14 16:01 ` Stephen Hemminger
2009-10-14 17:02 ` Brad Doctor
2009-10-14 19:33 ` Stephen Hemminger
2009-10-14 20:17 ` Luca Deri
2009-10-14 20:27 ` David Miller
2009-10-15 0:25 ` Eric Dumazet
2009-10-14 20:36 ` Evgeniy Polyakov
2009-10-14 21:27 ` Ben Greear
2009-10-14 21:34 ` Luca Deri
2009-10-14 21:49 ` David Miller
2009-10-14 23:29 ` Ben Greear
2009-10-15 7:02 ` Evgeniy Polyakov
2009-10-15 7:22 ` David Miller
2009-10-15 16:33 ` Ben Greear
2009-10-18 12:45 ` Harald Welte
2009-10-18 12:43 ` Harald Welte
2009-10-18 14:18 ` Evgeniy Polyakov
2009-10-14 16:46 ` Jarek Poplawski
2009-10-14 17:02 ` Brad Doctor
2009-10-14 17:18 ` Jarek Poplawski
2009-10-18 12:47 ` [OT] ntop / GPL (was Re: PF_RING: Include in main line kernel?) Harald Welte
2009-10-19 5:55 ` Jarek Poplawski
2009-10-19 7:12 ` Jarek Poplawski
2009-10-14 18:19 ` PF_RING: Include in main line kernel? Brent Cook
2009-10-14 19:54 ` Luca Deri
2009-10-14 20:15 ` David Miller
2009-10-14 20:26 ` Luca Deri
2009-10-14 20:29 ` David Miller
2009-10-14 20:34 ` Luca Deri
2009-10-14 20:50 ` Mark Smith [this message]
2009-10-18 12:56 ` Harald Welte
2009-10-18 12:50 ` Harald Welte
2009-10-18 14:50 ` Evgeniy Polyakov
2009-10-15 7:35 ` Rémi Denis-Courmont
2009-10-18 12:38 ` Harald Welte
2009-10-18 17:37 ` Luca Deri
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=20091015072041.6ebae736@opy.nosense.org \
--to=lk-netdev@lk-netdev.nosense.org \
--cc=bcook@bpointsys.com \
--cc=brad.doctor@gmail.com \
--cc=davem@davemloft.net \
--cc=deri@ntop.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.