Netdev List
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, shm@cumulusnetworks.com
Subject: Re: [PATCH net-next] inetpeer: Add support for VRFs
Date: Mon, 24 Aug 2015 02:15:14 +0200	[thread overview]
Message-ID: <20150824001514.GD21926@pox.localdomain> (raw)
In-Reply-To: <1440339964-16075-1-git-send-email-dsa@cumulusnetworks.com>

On 08/23/15 at 08:26am, David Ahern wrote:
> inetpeer caches based on address only, so duplicate IP addresses within
> a namespace return the same cached entry. Similar to IP fragments handle
> duplicate addresses across VRFs by adding the VRF master device index to
> the lookup.

We have a lot of other places which use the address only. Are you
going to add the VRF id to all these places as well?

  reply	other threads:[~2015-08-24  0:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-23 14:26 [PATCH net-next] inetpeer: Add support for VRFs David Ahern
2015-08-24  0:15 ` Thomas Graf [this message]
2015-08-24  2:01   ` David Ahern
2015-08-25 17:37     ` Thomas Graf
2015-08-25 20:47     ` David Miller
2015-08-25 22:41       ` David Ahern
2015-08-25 22:52         ` 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=20150824001514.GD21926@pox.localdomain \
    --to=tgraf@suug.ch \
    --cc=dsa@cumulusnetworks.com \
    --cc=netdev@vger.kernel.org \
    --cc=shm@cumulusnetworks.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