All of lore.kernel.org
 help / color / mirror / Atom feed
From: roopa <roopa@cumulusnetworks.com>
To: sfeldma@gmail.com
Cc: netdev@vger.kernel.org, davem@davemloft.net, jiri@resnulli.us
Subject: Re: [PATCH net-next v2 4/4] switchdev: don't support custom ip rules, for now
Date: Mon, 02 Mar 2015 06:36:15 -0800	[thread overview]
Message-ID: <54F4755F.6020205@cumulusnetworks.com> (raw)
In-Reply-To: <1425290777-22702-5-git-send-email-sfeldma@gmail.com>

On 3/2/15, 2:06 AM, sfeldma@gmail.com wrote:
> From: Scott Feldman <sfeldma@gmail.com>
>
> Keep switchdev FIB offload model simple for now and don't allow custom ip
> rules.
>
> Signed-off-by: Scott Feldman <sfeldma@gmail.com>

I don't see a need to do this. And seems very aggressive.
Also, note that the rules in a system can be on non-hw accelerated ports.

Until rules are hw accelerated, its ok to document this limitation for 
hw accelerated routes in my opinion.

  reply	other threads:[~2015-03-02 14:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 10:06 [PATCH net-next v2 0/4] switchdev: add IPv4 routing offload sfeldma
2015-03-02 10:06 ` [PATCH net-next v2 1/4] rtnetlink: add RTNH_F_EXTERNAL flag for fib offload sfeldma
2015-03-02 10:06 ` [PATCH net-next v2 2/4] net: add IPv4 routing FIB support for switchdev sfeldma
2015-03-02 14:30   ` roopa
2015-03-02 17:10     ` Scott Feldman
2015-03-02 19:24       ` roopa
2015-03-02 22:27   ` Samudrala, Sridhar
2015-03-02 22:31     ` David Miller
2015-03-02 10:06 ` [PATCH net-next v2 3/4] rocker: implement IPv4 fib offloading sfeldma
2015-03-02 10:06 ` [PATCH net-next v2 4/4] switchdev: don't support custom ip rules, for now sfeldma
2015-03-02 14:36   ` roopa [this message]
2015-03-02 17:00     ` Scott Feldman
2015-03-02 19:09       ` roopa
2015-03-02 20:40         ` David Miller
2015-03-02 20:30       ` David Miller
2015-03-02 20:10     ` 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=54F4755F.6020205@cumulusnetworks.com \
    --to=roopa@cumulusnetworks.com \
    --cc=davem@davemloft.net \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=sfeldma@gmail.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 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.