netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taehee Yoo <ap420073@gmail.com>
To: Breno Leitao <leitao@debian.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	horms@kernel.org, dsahern@kernel.org
Subject: Re: [PATCH net-next 1/2] net: amt: Move stats allocation to core
Date: Mon, 11 Mar 2024 12:46:42 +0900	[thread overview]
Message-ID: <8b013d18-2568-46d5-a808-ce9cc1b2ff98@gmail.com> (raw)
In-Reply-To: <20240308162606.1597287-1-leitao@debian.org>



On 3/9/24 1:26 AM, Breno Leitao wrote:
> With commit 34d21de99cea9 ("net: Move {l,t,d}stats allocation to core and
> convert veth & vrf"), stats allocation could be done on net core instead
> of this driver.
> 
> With this new approach, the driver doesn't have to bother with error
> handling (allocation failure checking, making sure free happens in the
> right spot, etc). This is core responsibility now.
> 
> Move amt driver to leverage the core allocation.
> 
> Signed-off-by: Breno Leitao <leitao@debian.org>
> ---
>   drivers/net/amt.c | 9 ++-------
>   1 file changed, 2 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/net/amt.c b/drivers/net/amt.c
> index 68e79b1272f6..cb31d1990660 100644
> --- a/drivers/net/amt.c
> +++ b/drivers/net/amt.c
> @@ -3063,15 +3063,10 @@ static int amt_dev_init(struct net_device *dev)
>   	int err;
>   
>   	amt->dev = dev;
> -	dev->tstats = netdev_alloc_pcpu_stats(struct pcpu_sw_netstats);
> -	if (!dev->tstats)
> -		return -ENOMEM;
>   
>   	err = gro_cells_init(&amt->gro_cells, dev);
> -	if (err) {
> -		free_percpu(dev->tstats);
> +	if (err)
>   		return err;
> -	}
>   
>   	return 0;
>   }
> @@ -3081,7 +3076,6 @@ static void amt_dev_uninit(struct net_device *dev)
>   	struct amt_dev *amt = netdev_priv(dev);
>   
>   	gro_cells_destroy(&amt->gro_cells);
> -	free_percpu(dev->tstats);
>   }
>   
>   static const struct net_device_ops amt_netdev_ops = {
> @@ -3111,6 +3105,7 @@ static void amt_link_setup(struct net_device *dev)
>   	dev->hw_features	|= NETIF_F_SG | NETIF_F_HW_CSUM;
>   	dev->hw_features	|= NETIF_F_FRAGLIST | NETIF_F_RXCSUM;
>   	dev->hw_features	|= NETIF_F_GSO_SOFTWARE;
> +	dev->pcpu_stat_type	= NETDEV_PCPU_STAT_TSTATS;
>   	eth_hw_addr_random(dev);
>   	eth_zero_addr(dev->broadcast);
>   	ether_setup(dev);

Reviewed-by: Taehee Yoo <ap420073@gmail.com>

  parent reply	other threads:[~2024-03-11  3:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 16:26 [PATCH net-next 1/2] net: amt: Move stats allocation to core Breno Leitao
2024-03-08 16:26 ` [PATCH net-next 2/2] net: amt: Remove generic .ndo_get_stats64 Breno Leitao
2024-03-11  3:47   ` Taehee Yoo
2024-03-11  3:46 ` Taehee Yoo [this message]
2024-03-11 22:50 ` [PATCH net-next 1/2] net: amt: Move stats allocation to core patchwork-bot+netdevbpf

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=8b013d18-2568-46d5-a808-ce9cc1b2ff98@gmail.com \
    --to=ap420073@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).