From: "Yuan, Linyu (NSB - CN/Shanghai)" <linyu.yuan@nokia-sbell.com>
To: Madalin-cristian Bucur <madalin.bucur@nxp.com>,
yuan linyu <cugyly@163.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>
Subject: RE: [PATCH net-next] net: dpaa: remove init which already done in per-cpu allocation
Date: Mon, 30 Oct 2017 05:12:29 +0000 [thread overview]
Message-ID: <2673700892724b47842afbf3ab36c541@nokia-sbell.com> (raw)
In-Reply-To: <DB3PR0402MB3849E758B1A2AD5FEF80DC27EC590@DB3PR0402MB3849.eurprd04.prod.outlook.com>
Hi,
devm_alloc_percpu() will allocate per-cpu memory and memset allocated block content to 0.
> -----Original Message-----
> From: Madalin-cristian Bucur [mailto:madalin.bucur@nxp.com]
> Sent: Monday, October 30, 2017 1:08 PM
> To: yuan linyu; netdev@vger.kernel.org
> Cc: David S . Miller; Yuan, Linyu (NSB - CN/Shanghai)
> Subject: RE: [PATCH net-next] net: dpaa: remove init which already done in
> per-cpu allocation
>
> Hi Yuan,
>
> Can you please give more details about this change you are proposing?
>
> Regards,
> Madalin
>
> > -----Original Message-----
> > From: netdev-owner@vger.kernel.org
> [mailto:netdev-owner@vger.kernel.org]
> > On Behalf Of yuan linyu
> > Sent: Sunday, October 29, 2017 3:49 AM
> > To: netdev@vger.kernel.org
> > Cc: David S . Miller <davem@davemloft.net>; yuan linyu
> > <Linyu.Yuan@alcatel-sbell.com.cn>
> > Subject: [PATCH net-next] net: dpaa: remove init which already done in
> > per-cpu allocation
> >
> > From: yuan linyu <Linyu.Yuan@alcatel-sbell.com.cn>
> >
> > Signed-off-by: yuan linyu <Linyu.Yuan@alcatel-sbell.com.cn>
> > ---
> > drivers/net/ethernet/freescale/dpaa/dpaa_eth.c | 4 ----
> > 1 file changed, 4 deletions(-)
> >
> > diff --git a/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
> > b/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
> > index a8d0be8..1ccc316 100644
> > --- a/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
> > +++ b/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
> > @@ -2814,10 +2814,6 @@ static int dpaa_eth_probe(struct
> platform_device
> > *pdev)
> > err = -ENOMEM;
> > goto free_dpaa_fqs;
> > }
> > - for_each_possible_cpu(i) {
> > - percpu_priv = per_cpu_ptr(priv->percpu_priv, i);
> > - memset(percpu_priv, 0, sizeof(*percpu_priv));
> > - }
> >
> > priv->num_tc = 1;
> > netif_set_real_num_tx_queues(net_dev, priv->num_tc *
> > DPAA_TC_TXQ_NUM);
> > --
> > 2.7.4
> >
next prev parent reply other threads:[~2017-10-30 5:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 1:48 [PATCH net-next] net: dpaa: remove init which already done in per-cpu allocation yuan linyu
2017-10-30 5:08 ` Madalin-cristian Bucur
2017-10-30 5:12 ` Yuan, Linyu (NSB - CN/Shanghai) [this message]
2017-10-30 5:15 ` Madalin-cristian Bucur
2017-10-30 5:20 ` Yuan, Linyu (NSB - CN/Shanghai)
2017-10-30 5:56 ` Madalin-cristian Bucur
2017-10-30 6:15 ` Yuan, Linyu (NSB - CN/Shanghai)
2017-10-30 7:13 ` Madalin-cristian Bucur
2017-10-30 7:17 ` Madalin-cristian Bucur
2017-11-01 3:09 ` David Miller
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=2673700892724b47842afbf3ab36c541@nokia-sbell.com \
--to=linyu.yuan@nokia-sbell.com \
--cc=cugyly@163.com \
--cc=davem@davemloft.net \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.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).