From: Thierry Reding <treding@nvidia.com>
To: Joao Pinto <Joao.Pinto@synopsys.com>
Cc: <davem@davemloft.net>, <clabbe.montjoie@gmail.com>,
<niklas.cassel@axis.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH 4/4] net: stmmac: adding multiple napi mechanism
Date: Tue, 4 Apr 2017 21:28:49 +0200 [thread overview]
Message-ID: <20170404192849.GF24271@ulmo.ba.sec> (raw)
In-Reply-To: <7af29adf8064bf5bb55b5a4e9fb2a3f325c873a2.1491328304.git.jpinto@synopsys.com>
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
On Tue, Apr 04, 2017 at 06:54:27PM +0100, Joao Pinto wrote:
[...]
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
[...]
> @@ -1259,7 +1317,6 @@ static int init_dma_tx_desc_rings(struct net_device *dev)
> /* TX INITIALIZATION */
> for (i = 0; i < DMA_TX_SIZE; i++) {
> struct dma_desc *p;
> -
> if (priv->extend_desc)
> p = &((tx_q->dma_etx + i)->basic);
> else
I think checkpatch would complain about this now because we're supposed
to separate variable declarations from code by a single blank line.
> - netif_napi_add(ndev, &priv->napi, stmmac_poll, 64);
> + ret = alloc_dma_desc_resources(priv);
> + if (ret < 0) {
> + netdev_err(priv->dev, "%s: DMA descriptors allocation failed\n",
> + __func__);
> + goto init_dma_error;
> + }
> +
> + ret = init_dma_desc_rings(priv->dev, GFP_KERNEL);
> + if (ret < 0) {
> + netdev_err(priv->dev, "%s: DMA descriptors initialization failed\n",
> + __func__);
> + goto init_dma_error;
> + }
> +
> + for (queue = 0; queue < priv->plat->rx_queues_to_use; queue++) {
> + struct stmmac_rx_queue *rx_q = &priv->rx_queue[queue];
> +
> + netif_napi_add(ndev, &rx_q->napi, stmmac_poll,
> + (8 * priv->plat->rx_queues_to_use));
> + }
Why is this moving to ->probe() now?
This works on Tegra186, so:
Reviewed-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-04-04 19:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 17:54 [PATCH 0/4 net-next] net: stmmac: adding multiple buffers Joao Pinto
2017-04-04 17:54 ` [PATCH 1/4] net: stmmac: break some functions into RX and TX scopes Joao Pinto
2017-04-04 17:54 ` [PATCH 2/4] net: stmmac: adding multiple buffers for rx Joao Pinto
2017-04-04 19:14 ` Thierry Reding
2017-04-04 19:15 ` Thierry Reding
2017-04-04 19:23 ` Thierry Reding
2017-04-04 17:54 ` [PATCH 3/4] net: stmmac: adding multiple buffers for TX Joao Pinto
2017-04-04 19:19 ` Thierry Reding
2017-04-04 17:54 ` [PATCH 4/4] net: stmmac: adding multiple napi mechanism Joao Pinto
2017-04-04 19:28 ` Thierry Reding [this message]
2017-04-04 18:57 ` [PATCH 1/4] net: stmmac: break some functions into RX and TX scopes Thierry Reding
2017-04-05 9:04 ` Joao Pinto
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=20170404192849.GF24271@ulmo.ba.sec \
--to=treding@nvidia.com \
--cc=Joao.Pinto@synopsys.com \
--cc=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=niklas.cassel@axis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.