[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4b0bcbf60537bcdfe8d184531788a9b6084be8f6.camel@mellanox.com>
Date: Tue, 21 Jan 2020 21:18:21 +0000
From: Saeed Mahameed <saeedm@...lanox.com>
To: Vlad Buslov <vladbu@...lanox.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"jiri@...nulli.us" <jiri@...nulli.us>,
Paul Blakey <paulb@...lanox.com>,
Oz Shlomo <ozsh@...lanox.com>,
"jakub.kicinski@...ronome.com" <jakub.kicinski@...ronome.com>,
"davem@...emloft.net" <davem@...emloft.net>
Subject: Re: [PATCH net-next 00/13] Handle multi chain hardware misses
On Tue, 2020-01-21 at 18:16 +0200, Paul Blakey wrote:
> Note that miss path handling of multi-chain rules is a required
> infrastructure
> for connection tracking hardware offload. The connection tracking
> offload
> series will follow this one.
Hi Dave and Jakub,
As Paul explained this is part one of two parts series,
Assuming the review will go with no issues i would like to suggest the
following acceptance options:
option 1) I can create a separate side branch for connection tracking
offload and once Paul submits the final patch of this feature and the
mailing list review is complete, i can send to you full pull request
with everything included ..
option 2) you to apply directly to net-next both patchsets
individually. (the normal process)
Please let me know what works better for you.
Personally I prefer option 1) so we won't endup stuck with only one
half of the connection tracking series if the review of the 2nd part
doesn't go as planned.
Thanks,
Saeed
Powered by blists - more mailing lists