From: "Timo Teräs" <timo.teras@iki.fi>
To: netdev@vger.kernel.org
Subject: CONFIG_ARPD help text
Date: Thu, 11 Jun 2009 21:28:21 +0300 [thread overview]
Message-ID: <4A314CC5.9090505@iki.fi> (raw)
Hi,
I just re-read again the CONFIG_ARPD help text. It says it's
"experimental and also obsolete".
But as opennhrp relies on this, and has shown the usefulness for
this interface - it can be used to implement other protocols that
resolve neighbor address than ARP in userland. In this case the
NHRP protocol.
Would it be acceptable to remove the designation as "obsolete"?
Also, I'm running the opennhrp on production with reasonable
size network (100+ nodes in gre subnet). And with the fix I sent
previously it seems to work very stable. Is there something more
to be done, or could the "experimental" marking be removed also?
I could also update the help to explain where the option is useful.
Or should the option be renamed to something like NEIGH_NETLINK?
It also seems that IPv6 supports CONFIG_ARPD so it should probably
be moved from net/ipv4/Kconfig to likely net/core/Kconfig?
Thanks,
Timo
next reply other threads:[~2009-06-11 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 18:28 Timo Teräs [this message]
2009-06-12 3:59 ` CONFIG_ARPD help text David Miller
2009-06-12 5:38 ` [PATCH] ipv4: update ARPD " Timo Teras
2009-06-14 6:38 ` David 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=4A314CC5.9090505@iki.fi \
--to=timo.teras@iki.fi \
--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 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).