From: Simon Horman <simon.horman@netronome.com>
To: David Miller <davem@davemloft.net>
Cc: wenxu@ucloud.cn, netdev@vger.kernel.org, pablo@netfilter.org,
vladbu@mellanox.com
Subject: Re: [PATCH net v5 0/4] several fixes for indirect flow_blocks offload
Date: Mon, 22 Jun 2020 11:13:21 +0200 [thread overview]
Message-ID: <20200622091320.GA24715@netronome.com> (raw)
In-Reply-To: <20200619.201342.2288126609984082133.davem@davemloft.net>
On Fri, Jun 19, 2020 at 08:13:42PM -0700, David Miller wrote:
> From: wenxu@ucloud.cn
> Date: Thu, 18 Jun 2020 20:49:07 +0800
>
> > From: wenxu <wenxu@ucloud.cn>
> >
> > v2:
> > patch2: store the cb_priv of representor to the flow_block_cb->indr.cb_priv
> > in the driver. And make the correct check with the statments
> > this->indr.cb_priv == cb_priv
> >
> > patch4: del the driver list only in the indriect cleanup callbacks
> >
> > v3:
> > add the cover letter and changlogs.
> >
> > v4:
> > collapsed 1/4, 2/4, 4/4 in v3 to one fix
> > Add the prepare patch 1 and 2
> >
> > v5:
> > patch1: place flow_indr_block_cb_alloc() right before
> > flow_indr_dev_setup_offload() to avoid moving flow_block_indr_init()
> >
> > This series fixes commit 1fac52da5942 ("net: flow_offload: consolidate
> > indirect flow_block infrastructure") that revists the flow_block
> > infrastructure.
> >
> > patch #1 #2: prepare for fix patch #3
> > add and use flow_indr_block_cb_alloc/remove function
> >
> > patch #3: fix flow_indr_dev_unregister path
> > If the representor is removed, then identify the indirect flow_blocks
> > that need to be removed by the release callback and the port representor
> > structure. To identify the port representor structure, a new
> > indr.cb_priv field needs to be introduced. The flow_block also needs to
> > be removed from the driver list from the cleanup path
> >
> >
> > patch#4 fix block->nooffloaddevcnt warning dmesg log.
> > When a indr device add in offload success. The block->nooffloaddevcnt
> > should be 0. After the representor go away. When the dir device go away
> > the flow_block UNBIND operation with -EOPNOTSUPP which lead the warning
> > demesg log.
> > The block->nooffloaddevcnt should always count for indr block.
> > even the indr block offload successful. The representor maybe
> > gone away and the ingress qdisc can work in software mode.
>
> Series applied, thank you.
Hi Dave,
when you get a chance could you pull net into net-next
to get these changes there?
Thanks!
prev parent reply other threads:[~2020-06-22 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 12:49 [PATCH net v5 0/4] several fixes for indirect flow_blocks offload wenxu
2020-06-18 12:49 ` [PATCH net v5 1/4] flow_offload: add flow_indr_block_cb_alloc/remove function wenxu
2020-06-18 12:49 ` [PATCH net v5 2/4] flow_offload: use " wenxu
2020-06-18 12:49 ` [PATCH net v5 3/4] net: flow_offload: fix flow_indr_dev_unregister path wenxu
2020-06-18 12:49 ` [PATCH net v5 4/4] net/sched: cls_api: fix nooffloaddevcnt warning dmesg log wenxu
2020-06-19 7:10 ` [PATCH net v5 0/4] several fixes for indirect flow_blocks offload Simon Horman
2020-06-20 3:13 ` David Miller
2020-06-22 9:13 ` Simon Horman [this message]
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=20200622091320.GA24715@netronome.com \
--to=simon.horman@netronome.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=vladbu@mellanox.com \
--cc=wenxu@ucloud.cn \
/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).