From: Gregory Rose <gvrose8192@gmail.com>
To: Taehee Yoo <ap420073@gmail.com>,
davem@davemloft.net, pshelar@ovn.org, netdev@vger.kernel.org,
dev@openvswitch.org
Subject: Re: [ovs-dev] [PATCH net-next] net: openvswitch: do not update max_headroom if new headroom is equal to old headroom
Date: Fri, 12 Jul 2019 09:18:39 -0700 [thread overview]
Message-ID: <61e34406-74af-e9a4-0309-a31ee1f819a4@gmail.com> (raw)
In-Reply-To: <20190705160809.5202-1-ap420073@gmail.com>
On 7/5/2019 9:08 AM, Taehee Yoo wrote:
> When a vport is deleted, the maximum headroom size would be changed.
> If the vport which has the largest headroom is deleted,
> the new max_headroom would be set.
> But, if the new headroom size is equal to the old headroom size,
> updating routine is unnecessary.
>
> Signed-off-by: Taehee Yoo <ap420073@gmail.com>
> ---
> net/openvswitch/datapath.c | 39 +++++++++++++++++++++++++++-----------
> 1 file changed, 28 insertions(+), 11 deletions(-)
>
> diff --git a/net/openvswitch/datapath.c b/net/openvswitch/datapath.c
> index 33b388103741..892287d06c17 100644
> --- a/net/openvswitch/datapath.c
> +++ b/net/openvswitch/datapath.c
> @@ -1958,10 +1958,9 @@ static struct vport *lookup_vport(struct net *net,
>
> }
>
> -/* Called with ovs_mutex */
> -static void update_headroom(struct datapath *dp)
> +static unsigned int ovs_get_max_headroom(struct datapath *dp)
> {
> - unsigned dev_headroom, max_headroom = 0;
> + unsigned int dev_headroom, max_headroom = 0;
> struct net_device *dev;
> struct vport *vport;
> int i;
> @@ -1975,10 +1974,19 @@ static void update_headroom(struct datapath *dp)
> }
> }
>
> - dp->max_headroom = max_headroom;
> + return max_headroom;
> +}
> +
> +/* Called with ovs_mutex */
> +static void ovs_update_headroom(struct datapath *dp, unsigned int new_headroom)
> +{
> + struct vport *vport;
> + int i;
> +
> + dp->max_headroom = new_headroom;
> for (i = 0; i < DP_VPORT_HASH_BUCKETS; i++)
> hlist_for_each_entry_rcu(vport, &dp->ports[i], dp_hash_node)
> - netdev_set_rx_headroom(vport->dev, max_headroom);
> + netdev_set_rx_headroom(vport->dev, new_headroom);
> }
>
> static int ovs_vport_cmd_new(struct sk_buff *skb, struct genl_info *info)
> @@ -1989,6 +1997,7 @@ static int ovs_vport_cmd_new(struct sk_buff *skb, struct genl_info *info)
> struct sk_buff *reply;
> struct vport *vport;
> struct datapath *dp;
> + unsigned int new_headroom;
> u32 port_no;
> int err;
>
> @@ -2050,8 +2059,10 @@ static int ovs_vport_cmd_new(struct sk_buff *skb, struct genl_info *info)
> info->snd_portid, info->snd_seq, 0,
> OVS_VPORT_CMD_NEW);
>
> - if (netdev_get_fwd_headroom(vport->dev) > dp->max_headroom)
> - update_headroom(dp);
> + new_headroom = netdev_get_fwd_headroom(vport->dev);
> +
> + if (new_headroom > dp->max_headroom)
> + ovs_update_headroom(dp, new_headroom);
> else
> netdev_set_rx_headroom(vport->dev, dp->max_headroom);
>
> @@ -2122,11 +2133,12 @@ static int ovs_vport_cmd_set(struct sk_buff *skb, struct genl_info *info)
>
> static int ovs_vport_cmd_del(struct sk_buff *skb, struct genl_info *info)
> {
> - bool must_update_headroom = false;
> + bool update_headroom = false;
> struct nlattr **a = info->attrs;
> struct sk_buff *reply;
> struct datapath *dp;
> struct vport *vport;
> + unsigned int new_headroom;
> int err;
>
> reply = ovs_vport_cmd_alloc_info();
> @@ -2152,12 +2164,17 @@ static int ovs_vport_cmd_del(struct sk_buff *skb, struct genl_info *info)
> /* the vport deletion may trigger dp headroom update */
> dp = vport->dp;
> if (netdev_get_fwd_headroom(vport->dev) == dp->max_headroom)
> - must_update_headroom = true;
> + update_headroom = true;
> +
> netdev_reset_rx_headroom(vport->dev);
> ovs_dp_detach_port(vport);
>
> - if (must_update_headroom)
> - update_headroom(dp);
> + if (update_headroom) {
> + new_headroom = ovs_get_max_headroom(dp);
> +
> + if (new_headroom < dp->max_headroom)
> + ovs_update_headroom(dp, new_headroom);
> + }
> ovs_unlock();
>
> ovs_notify(&dp_vport_genl_family, reply, info);
I did a compile test and ran the OVS kernel self-test suite. Looks OK
to me.
Tested-by: Greg Rose <gvrose8192@gmail.com>
Reviewed-by: Greg Rose <gvrose8192@gmail.com>
next prev parent reply other threads:[~2019-07-12 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 16:08 [PATCH net-next] net: openvswitch: do not update max_headroom if new headroom is equal to old headroom Taehee Yoo
2019-07-08 23:08 ` David Miller
2019-07-08 23:18 ` [ovs-dev] " Gregory Rose
2019-07-08 23:22 ` Gregory Rose
2019-07-11 21:07 ` Pravin Shelar
2019-07-11 23:55 ` Gregory Rose
2019-07-12 16:18 ` Gregory Rose [this message]
2019-07-12 22:18 ` David Miller
2019-07-12 23:11 ` Gregory Rose
2019-07-15 18:15 ` Pravin Shelar
2019-07-16 12:28 ` Taehee Yoo
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=61e34406-74af-e9a4-0309-a31ee1f819a4@gmail.com \
--to=gvrose8192@gmail.com \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
/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).