From: Paul Blakey <paulb@mellanox.com>
To: Pravin B Shelar <pshelar@ovn.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Justin Pettit <jpettit@nicira.com>,
Simon Horman <simon.horman@netronome.com>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Vlad Buslov <vladbu@mellanox.com>
Cc: Jiri Pirko <jiri@mellanox.com>, Roi Dayan <roid@mellanox.com>,
Yossi Kuperman <yossiku@mellanox.com>,
Rony Efraim <ronye@mellanox.com>, Oz Shlomo <ozsh@mellanox.com>
Subject: Re: [PATCH net-next v2] net: openvswitch: Set OvS recirc_id from tc chain index
Date: Tue, 20 Aug 2019 12:56:23 +0000 [thread overview]
Message-ID: <677eef11-7f6a-ffcd-6e1d-b1b6e885ac20@mellanox.com> (raw)
In-Reply-To: <1566304834-22836-1-git-send-email-paulb@mellanox.com>
Hey guys, sorry for spam, I used the --in-reply-to this time so it gets
to the original thread ("[PATCH net-next v2] net: openvswitch: Set OvS
recirc_id from tc chain index") ,
Ignore this thread and respond there if needed.
Thanks.
On 8/20/2019 3:40 PM, Paul Blakey wrote:
> Regarding the user_features change, I tested the above patch with this one in
> userspace that I'll send once this is accepted, togother with the rest
> of connection tracking offload patches.
>
> I also have a test for it, if anyone wants it.
>
> Patch is:
> lib/netdev-offloads-tc: Probe recirc tc sharing feature on first recirc_id rule
> [...]
next prev parent reply other threads:[~2019-08-20 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 12:40 [PATCH net-next v2] net: openvswitch: Set OvS recirc_id from tc chain index Paul Blakey
2019-08-20 12:56 ` Paul Blakey [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-20 12:30 Paul Blakey
2019-08-20 12:51 ` Paul Blakey
2019-08-22 3:57 ` David Miller
2019-08-25 14:11 ` Paul Blakey
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=677eef11-7f6a-ffcd-6e1d-b1b6e885ac20@mellanox.com \
--to=paulb@mellanox.com \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=jpettit@nicira.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ozsh@mellanox.com \
--cc=pshelar@ovn.org \
--cc=roid@mellanox.com \
--cc=ronye@mellanox.com \
--cc=simon.horman@netronome.com \
--cc=vladbu@mellanox.com \
--cc=yossiku@mellanox.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;
as well as URLs for NNTP newsgroup(s).