All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Ido Schimmel <idosch@idosch.org>, netdev@vger.kernel.org
Cc: davem@davemloft.net, jiri@mellanox.com,
	jakub.kicinski@netronome.com, roopa@cumulusnetworks.com,
	mlxsw@mellanox.com, Ido Schimmel <idosch@mellanox.com>
Subject: Re: [PATCH net-next 01/10] ipv4: Replace route in list before notifying
Date: Wed, 8 Jan 2020 11:33:45 -0700	[thread overview]
Message-ID: <1d1ecb8e-e753-0f2c-7463-721d1aadee83@gmail.com> (raw)
In-Reply-To: <20200107154517.239665-2-idosch@idosch.org>

On 1/7/20 8:45 AM, Ido Schimmel wrote:
> From: Ido Schimmel <idosch@mellanox.com>
> 
> Subsequent patches will add an offload / trap indication to routes which
> will signal if the route is present in hardware or not.
> 
> After programming the route to the hardware, drivers will have to ask
> the IPv4 code to set the flags by passing the route's key.
> 
> In the case of route replace, the new route is notified before it is
> actually inserted into the FIB alias list. This can prevent simple
> drivers (e.g., netdevsim) that program the route to the hardware in the
> same context it is notified in from being able to set the flag.
> 
> Solve this by first inserting the new route to the list and rollback the
> operation in case the route was vetoed.
> 
> Signed-off-by: Ido Schimmel <idosch@mellanox.com>
> Reviewed-by: Jiri Pirko <jiri@mellanox.com>
> ---
>  net/ipv4/fib_trie.c | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)
> 

Reviewed-by: David Ahern <dsahern@gmail.com>



  reply	other threads:[~2020-01-08 18:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 15:45 [PATCH net-next 00/10] net: Add route offload indication Ido Schimmel
2020-01-07 15:45 ` [PATCH net-next 01/10] ipv4: Replace route in list before notifying Ido Schimmel
2020-01-08 18:33   ` David Ahern [this message]
2020-01-07 15:45 ` [PATCH net-next 02/10] ipv4: Encapsulate function arguments in a struct Ido Schimmel
2020-01-08 18:37   ` David Ahern
2020-01-09  8:26     ` Ido Schimmel
2020-01-07 15:45 ` [PATCH net-next 03/10] ipv4: Add "offload" and "trap" indications to routes Ido Schimmel
2020-01-09 15:47   ` David Ahern
2020-01-07 15:45 ` [PATCH net-next 04/10] ipv6: " Ido Schimmel
2020-01-09 15:48   ` David Ahern
2020-01-09 16:24   ` Roopa Prabhu
2020-01-07 15:45 ` [PATCH net-next 05/10] mlxsw: spectrum_router: Separate nexthop offload indication from route Ido Schimmel
2020-01-07 15:45 ` [PATCH net-next 06/10] mlxsw: spectrum_router: Set hardware flags for routes Ido Schimmel
2020-01-07 15:45 ` [PATCH net-next 07/10] netdevsim: fib: Add dummy implementation for FIB offload Ido Schimmel
2020-01-07 15:45 ` [PATCH net-next 08/10] selftests: forwarding: Add helpers and tests " Ido Schimmel
2020-01-07 15:45 ` [PATCH net-next 09/10] selftests: netdevsim: Add test for FIB offload API Ido Schimmel
2020-01-07 15:45 ` [PATCH net-next 10/10] selftests: mlxsw: " Ido Schimmel

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=1d1ecb8e-e753-0f2c-7463-721d1aadee83@gmail.com \
    --to=dsahern@gmail.com \
    --cc=davem@davemloft.net \
    --cc=idosch@idosch.org \
    --cc=idosch@mellanox.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=jiri@mellanox.com \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@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 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.