From: "David S. Miller" <davem@redhat.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: Restrict local IP announcements in ARP requests
Date: Wed, 11 Feb 2004 20:22:51 -0800 [thread overview]
Message-ID: <20040211202251.7b05102c.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0402100154010.1251@u.domain.uli>
On Tue, 10 Feb 2004 02:31:23 +0200 (EET)
Julian Anastasov <ja@ssi.bg> wrote:
> So, if hidden exists and is disabled it will not delay
> too much the processing but it is true that both arp_rcv and
> arp_solicit become more and more loaded with ugly checks.
The hidden patch does a hundred different things, that's what makes
it so undigestable. :)
Let us assume your arp_announce patch is applied. Given that, plus the
things you've mentioned, only a tiny piece of functionality is
really needed from that hidden patch.
Why don't you extract out just the needed part, and toss together
an email with that patch explaining that specific behavior change?
Thanks.
next prev parent reply other threads:[~2004-02-12 4:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 9:59 Restrict local IP announcements in ARP requests Julian Anastasov
2004-02-09 22:08 ` David S. Miller
2004-02-09 22:20 ` David S. Miller
2004-02-09 23:06 ` Julian Anastasov
2004-02-09 23:10 ` David S. Miller
2004-02-10 0:31 ` Julian Anastasov
2004-02-12 4:22 ` David S. Miller [this message]
2004-02-15 10:04 ` Julian Anastasov
2004-02-18 3:07 ` David S. Miller
2004-02-18 8:22 ` Julian Anastasov
2004-02-18 21:03 ` David S. Miller
2004-02-10 1:00 ` Julian Anastasov
2004-02-12 4:16 ` David S. Miller
2004-02-12 23:50 ` Julian Anastasov
2004-02-14 7:24 ` David S. Miller
2004-02-14 12:03 ` Julian Anastasov
2004-02-14 20:37 ` 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=20040211202251.7b05102c.davem@redhat.com \
--to=davem@redhat.com \
--cc=ja@ssi.bg \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).