From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: add support for STMicroelectronics Ethernet controllers.
Date: Tue, 06 Oct 2009 14:38:26 +0200 [thread overview]
Message-ID: <4ACB3A42.9070600@st.com> (raw)
In-Reply-To: <4ACB1B95.4090701@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Eric,
many thanks for your prompt feedback.
Eric Dumazet wrote:
> Giuseppe CAVALLARO a écrit :
>
>> +static int stmmac_sw_tso(struct stmmac_priv *priv, struct sk_buff *skb)
[snip]
>
> So stmmac_sw_tso() calls stmmac_xmit() for each seg skb.
>
> But stmmac_sw_tso() was called from stmmac_xmit(),
> with priv->tx_lock locked, so I suspect something is wrong.
Yes, you are right on this.
I'm going to remove it. Indeed, I observed no gain during my performance
tests. I had added it just to become familiar with this.
Note also that our chips do not have the segmentation offloading in Hw.
Thanks for this observation.
> Also please change various
>
> + mac = kmalloc(sizeof(const struct mac_device_info), GFP_KERNEL);
> + memset(mac, 0, sizeof(struct mac_device_info));
> +
>
> + mac = kmalloc(sizeof(const struct mac_device_info), GFP_KERNEL);
> + memset(mac, 0, sizeof(struct mac_device_info));
> +
>
> to use kzalloc(), and of course, you should check kmalloc()/kzalloc() dont return NULL !
>
Yes I'll do that too.
> Also :
>
> +static int stmmac_clean_tx(struct net_device *dev)
[snip]
> + if (skb != NULL) {
> + /*
> + * If there's room in the queue (limit it to size)
> + * we add this skb back into the pool,
> + * if it's the right size.
> + */
> + if ((skb_queue_len(&priv->rx_recycle) <
> + priv->dma_rx_size) &&
> + skb_recycle_check(skb, priv->dma_buf_sz))
> + __skb_queue_head(&priv->rx_recycle, skb);
> + else
> + dev_kfree_skb_any(skb);
>
> Why call dev_kfree_skb_any() here ? From NAPI context it is overkill.
The logic behind this piece of code should be the same one adopted in
other drivers like gianfar, ucc_geth and mv643xx_eth. What am I missing?
> static int stmmac_poll(struct napi_struct *napi, int budget)
> +{
[snip]
> +
> + tx_cleaned = stmmac_clean_tx(dev);
> +
> + work_done = stmmac_rx(dev, budget);
> +
>
>
> + if (tx_cleaned)
> + return budget;
>
> Why tx_cleaned is used here to exit early ?
I've found interesting the approach used in gianfar (see commit
42199884594bc336c9185441cbed99a9324dab34).
Thanks again for the feedback.
Regards,
Peppe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkrLOjkACgkQ2Xo3j31MSSIM5ACgrTLJgwO84ooKkcoEaNMZ5bcy
iBUAoK+q677OnyeCdeNndFq92AmwNPoa
=r7WK
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-10-06 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 7:51 [PATCH] net: add support for STMicroelectronics Ethernet controllers Giuseppe CAVALLARO
2009-10-06 10:27 ` Eric Dumazet
2009-10-06 12:38 ` Giuseppe CAVALLARO [this message]
2009-10-06 13:35 ` Eric Dumazet
2009-10-06 13:42 ` Giuseppe CAVALLARO
2009-10-13 12:35 ` Giuseppe CAVALLARO
2009-10-14 4:07 ` Eric Dumazet
2009-10-14 6:58 ` Giuseppe CAVALLARO
2009-10-14 22:14 ` 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=4ACB3A42.9070600@st.com \
--to=peppe.cavallaro@st.com \
--cc=eric.dumazet@gmail.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).