All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@redhat.com>
To: Scott Feldman <sfeldma@gmail.com>
Cc: Netdev <netdev@vger.kernel.org>, "Jiří Pírko" <jiri@resnulli.us>,
	"john fastabend" <john.fastabend@gmail.com>,
	"Thomas Graf" <tgraf@suug.ch>,
	"Jamal Hadi Salim" <jhs@mojatatu.com>,
	"Andy Gospodarek" <andy@greyhouse.net>,
	"Roopa Prabhu" <roopa@cumulusnetworks.com>
Subject: Re: [PATCH net-next 1/3] net: add IPv4 routing FIB support for swdev
Date: Tue, 06 Jan 2015 21:26:56 +0100	[thread overview]
Message-ID: <1420576016.15181.21.camel@redhat.com> (raw)
In-Reply-To: <1420574353.15181.19.camel@stressinduktion.org>

On Di, 2015-01-06 at 20:59 +0100, Hannes Frederic Sowa wrote:
> Sorry, I haven't fully understood this. Does rocker first do a L3
> routing table lookup and *after* that does decide which nexthop to chose
> based on preferences in the action-set found at the leaf? My gut tells
> me that we cannot do a semantically equivalent to ip rules then, we
> would have to use ACLs then. Hmm...

Does rocker drop the packet if no match is found or can it pass the
packet onto the slowpath to the kernel?

  reply	other threads:[~2015-01-06 20:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02  3:29 [PATCH net-next 1/3] net: add IPv4 routing FIB support for swdev sfeldma
2015-01-02  5:49 ` roopa
2015-01-02  8:00   ` Scott Feldman
2015-01-02 11:39     ` Arad, Ronen
2015-01-02 17:20       ` Scott Feldman
2015-01-02 22:57       ` roopa
2015-01-02 20:55     ` roopa
2015-01-02 11:21   ` Arad, Ronen
2015-01-02 21:53     ` roopa
2015-01-06 13:58 ` Hannes Frederic Sowa
2015-01-06 17:51   ` Scott Feldman
2015-01-06 19:59     ` Hannes Frederic Sowa
2015-01-06 20:26       ` Hannes Frederic Sowa [this message]
2015-01-07  2:08       ` Shrijeet Mukherjee
2015-01-07 11:23         ` Hannes Frederic Sowa
2015-01-07 17:54           ` Shrijeet Mukherjee
2015-01-08 13:03             ` Hannes Frederic Sowa

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=1420576016.15181.21.camel@redhat.com \
    --to=hannes@redhat.com \
    --cc=andy@greyhouse.net \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=john.fastabend@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@cumulusnetworks.com \
    --cc=sfeldma@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.