From: David Miller <davem@davemloft.net>
To: ja@ssi.bg
Cc: netdev@vger.kernel.org, tgraf@suug.ch, jpirko@redhat.com,
herbert@gondor.hengli.com.au, eric.dumazet@gmail.com
Subject: Re: [PATCH v6 BONUS 4/3] ipv4: Store rtable entries directly in FIB
Date: Fri, 06 May 2011 10:57:14 -0700 (PDT) [thread overview]
Message-ID: <20110506.105714.193719418.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LFD.2.00.1105060944230.1435@ja.ssi.bg>
From: Julian Anastasov <ja@ssi.bg>
Date: Fri, 6 May 2011 12:12:26 +0300 (EEST)
> Caching results of __mkroute_output in NH does
> not work well for RTN_MULTICAST because ip_check_mc_rcu
> wants to further restrict local delivery depending on
> the source address and protocol.
I understand that multicast needs special handling.
I'm concentrating on unicast/broadcast at the moment because
there is a predominantly clear path for making that work.
prev parent reply other threads:[~2011-05-06 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 23:36 [PATCH v6 BONUS 4/3] ipv4: Store rtable entries directly in FIB David Miller
2011-05-06 9:12 ` Julian Anastasov
2011-05-06 17:57 ` David Miller [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=20110506.105714.193719418.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=herbert@gondor.hengli.com.au \
--cc=ja@ssi.bg \
--cc=jpirko@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).