From: Andrew Lunn <andrew@lunn.ch>
To: Shenwei Wang <shenwei.wang@nxp.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Wei Fang <wei.fang@nxp.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH 1/1] net: fec: using page pool to manage RX buffers
Date: Fri, 30 Sep 2022 22:15:09 +0200 [thread overview]
Message-ID: <YzdOTSNEUR2hi/dv@lunn.ch> (raw)
In-Reply-To: <20220930193751.1249054-1-shenwei.wang@nxp.com>
> +struct fec_enet_xdp_stats {
> + u64 xdp_pass;
> + u64 xdp_drop;
> + u64 xdp_xmit;
> + u64 xdp_redirect;
> + u64 xdp_xmit_err;
> + u64 xdp_tx;
> + u64 xdp_tx_err;
> +};
These are not used in this patch. Please don't add anything until it
is actually used. The danger is, when you add the actual increments,
we miss that they are u64 and so need protecting. If they are in the
same patch, it is much more obvious.
> +
> struct fec_enet_priv_tx_q {
> struct bufdesc_prop bd;
> unsigned char *tx_bounce[TX_RING_SIZE];
> @@ -532,7 +552,15 @@ struct fec_enet_priv_tx_q {
>
> struct fec_enet_priv_rx_q {
> struct bufdesc_prop bd;
> - struct sk_buff *rx_skbuff[RX_RING_SIZE];
> + struct fec_enet_priv_txrx_info rx_skb_info[RX_RING_SIZE];
> +
> + /* page_pool */
> + struct page_pool *page_pool;
> + struct xdp_rxq_info xdp_rxq;
> + struct fec_enet_xdp_stats stats;
> +
> + /* rx queue number, in the range 0-7 */
> + u8 id;
> };
>
> struct fec_stop_mode_gpr {
> @@ -644,6 +672,9 @@ struct fec_enet_private {
>
> struct imx_sc_ipc *ipc_handle;
>
> + /* XDP BPF Program */
> + struct bpf_prog *xdp_prog;
Not in this patch.
> fec_enet_alloc_rxq_buffers(struct net_device *ndev, unsigned int queue)
> {
> struct fec_enet_private *fep = netdev_priv(ndev);
> - unsigned int i;
> - struct sk_buff *skb;
> + int i, err;
> struct bufdesc *bdp;
> struct fec_enet_priv_rx_q *rxq;
>
> + dma_addr_t phys_addr;
> + struct page *page;
Reverse Christmas tree is messed up in this driver, but please don't
make it worse. int i, err; should probably be last, and don't add a
blank line.
Andrew
prev parent reply other threads:[~2022-09-30 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 19:37 [PATCH 1/1] net: fec: using page pool to manage RX buffers Shenwei Wang
2022-09-30 19:52 ` Andrew Lunn
2022-09-30 19:58 ` [EXT] " Shenwei Wang
2022-09-30 20:01 ` Andrew Lunn
2022-09-30 20:08 ` Shenwei Wang
2022-09-30 20:05 ` Andrew Lunn
2022-09-30 20:07 ` [EXT] " Shenwei Wang
2022-09-30 20:20 ` Andrew Lunn
2022-09-30 20:15 ` Andrew Lunn [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=YzdOTSNEUR2hi/dv@lunn.ch \
--to=andrew@lunn.ch \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=imx@lists.linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shenwei.wang@nxp.com \
--cc=wei.fang@nxp.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