From: David Miller <davem@davemloft.net>
To: ja@ssi.bg
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net v2 0/6] ipv4: Changes for rt_gateway
Date: Mon, 08 Oct 2012 17:43:10 -0400 (EDT) [thread overview]
Message-ID: <20121008.174310.138554100330578332.davem@davemloft.net> (raw)
In-Reply-To: <1349732480-19978-1-git-send-email-ja@ssi.bg>
From: Julian Anastasov <ja@ssi.bg>
Date: Tue, 9 Oct 2012 00:41:14 +0300
> This patchset fixes some problems for the routing caused
> by the new rt_gateway semantics. What started as a fix for
> IPVS-DR ended as fixes for more problems. To solve the IPVS
> problem I decided to name the flag FLOWI_FLAG_KNOWN_NH, so that
> we can even get route cached in FNHE or FIB NH.
>
> Different flag FLOWI_FLAG_RT_NOCACHE could be equally good
> for IPVS, we again would be able to use data from fnhe but working
> with cached routes should be preferred. If there is no FNHE, the
> common case is IPVS to get uncached route, of course, IPVS caches
> it itself.
>
> Patches 1-3 are fixes not related to IPVS problem,
> 4 and 5 add code that will be used by IPVS in patch 6.
This series looks great, applied, thanks Julian.
prev parent reply other threads:[~2012-10-08 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 21:41 [PATCH net v2 0/6] ipv4: Changes for rt_gateway Julian Anastasov
2012-10-08 21:41 ` [PATCH net v2 1/6] ipv4: fix sending of redirects Julian Anastasov
2012-10-08 21:41 ` [PATCH net v2 2/6] ipv4: fix forwarding for strict source routes Julian Anastasov
2012-10-08 21:41 ` [PATCH net v2 3/6] ipv4: make sure nh_pcpu_rth_output is always allocated Julian Anastasov
2012-10-08 21:41 ` [PATCH net v2 4/6] ipv4: introduce rt_uses_gateway Julian Anastasov
2012-10-08 21:41 ` [PATCH net v2 5/6] ipv4: Add FLOWI_FLAG_KNOWN_NH Julian Anastasov
2012-10-08 21:41 ` [PATCH net v2 6/6] ipvs: fix ARP resolving for direct routing mode Julian Anastasov
2012-10-08 21:43 ` 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=20121008.174310.138554100330578332.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ja@ssi.bg \
--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