From: Ben Greear <greearb@candelatech.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@muc.de>
Subject: Re: [PATCH] arp_filter patch for 2.4.4 kernel.
Date: Sun, 06 May 2001 00:20:55 -0700 [thread overview]
Message-ID: <3AF4FB57.BA55A651@candelatech.com> (raw)
In-Reply-To: <3AF4720F.35574FDD@candelatech.com> <15092.32371.139915.110859@pizda.ninka.net> <3AF49617.1B3C48AF@candelatech.com> <15092.37426.648280.631914@pizda.ninka.net>
"David S. Miller" wrote:
>
> Ben Greear writes:
> > No idea, haven't tried to use netfilter. With this patch, though,
> > it's as easy as:
>
> I know, the problem is if some existing facility can be made
> to do it, I'd rather it be done that way.
Would requiring netfilter to be used slow down the fast path
for packets in any way? The current arp-filter code will not,
as far as I can tell, and if the netfilter overhead is significant,
that may be a good reason to accept the patch, or the alternative
one proposed a few mails back...
--
Ben Greear <greearb@candelatech.com> <Ben_Greear@excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2001-05-06 7:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 21:35 [PATCH] arp_filter patch for 2.4.4 kernel Ben Greear
2001-05-05 22:28 ` David S. Miller
2001-05-05 22:53 ` dean gaudet
2001-05-05 22:57 ` dean gaudet
2001-05-05 23:27 ` David S. Miller
2001-05-06 8:34 ` Andi Kleen
2001-05-06 16:35 ` Mark Hahn
2001-05-06 0:08 ` Ben Greear
2001-05-05 23:52 ` David S. Miller
2001-05-06 7:20 ` Ben Greear [this message]
2001-05-06 8:40 ` Andi Kleen
2001-05-13 22:39 ` Harald Welte
2001-05-07 16:35 ` Matthew Kirkwood
2001-05-13 6:37 ` Ben Greear
2001-05-13 7:45 ` David S. Miller
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=3AF4FB57.BA55A651@candelatech.com \
--to=greearb@candelatech.com \
--cc=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--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