From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, devicetree@vger.kernel.org,
galak@codeaurora.org, netdev@vger.kernel.org,
richardcochran@gmail.com
Cc: linux-sh@vger.kernel.org,
Mitsuhiro Kimura <mitsuhiro.kimura.kc@renesas.com>,
Ben Hutchings <ben.hutchings@codethink.co.uk>
Subject: Re: [PATCH v3] Renesas Ethernet AVB driver
Date: Thu, 07 May 2015 21:10:36 +0000 [thread overview]
Message-ID: <554BD4CC.3020308@cogentembedded.com> (raw)
In-Reply-To: <553A9123.3010906@cogentembedded.com>
Hello.
On 04/24/2015 09:53 PM, Sergei Shtylyov wrote:
[...]
>>>>> +static int ravb_start_xmit(struct sk_buff *skb, struct net_device
>>>>> *ndev)
>>>>> +{
>>>>> + struct ravb_private *priv = netdev_priv(ndev);
>>>>> + struct ravb_tstamp_skb *ts_skb = NULL;
>>>>> + struct ravb_tx_desc *desc;
>>>>> + unsigned long flags;
>>>>> + void *buffer;
>>>>> + u32 entry;
>>>>> + u32 tccr;
>>>>> + int q;
>>>>> +
>>>>> + /* If skb needs TX timestamp, it is handled in network control
>>>>> queue */
>>>>> + q = (skb_shinfo(skb)->tx_flags & SKBTX_HW_TSTAMP) ? RAVB_NC :
>>>>> RAVB_BE;
>>>>> +
>>>>> + spin_lock_irqsave(&priv->lock, flags);
>>>>> + if (priv->cur_tx[q] - priv->dirty_tx[q] >= priv->num_tx_ring[q]
>>>>> - 4) {
>>>> What's so special about 4 here, you don't seem to be using 4 descriptors
>>> Not sure, this was clearly copied from sh_eth.c. Perhaps it's just a
>>> threshold for calling ravb_tx_free()...
>
>> Then 1 inclusive or 0 exclusive is probably what you should be comparing
>> to, otherwise you may just stop the tx queue earlier than needed.
> Will look into this...
OK, I've fixed this.
[...]
>>>>> + desc->ds = skb->len;
>>>>> + desc->dptr = dma_map_single(&ndev->dev, buffer, skb->len,
>>>>> + DMA_TO_DEVICE);
>>>>> + if (dma_mapping_error(&ndev->dev, desc->dptr)) {
>>>>> + dev_kfree_skb_any(skb);
>>>>> + priv->tx_skb[q][entry] = NULL;
>>>> Don't you need to make sure this NULL is properly seen by ravb_tx_free()?
>>> You mean doing this before releasing the spinlock? Or what?
>> Yes, the locking your transmit function seems to open windows during
>> which it is possible for the interrupt handler running on another CPU to
>> mess up with the data you are using here.
> Will look into that too...
I have looked into the code and I must admit I don't understand how the
data can be messed up with. ravb_tx_free() only advances 'priv->dirty_tx' and
doesn't go beyond (or change) 'priv->cur_tx' which is used here...
>> --
>> Florian
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, devicetree@vger.kernel.org,
galak@codeaurora.org, netdev@vger.kernel.org,
richardcochran@gmail.com
Cc: linux-sh@vger.kernel.org,
Mitsuhiro Kimura <mitsuhiro.kimura.kc@renesas.com>,
Ben Hutchings <ben.hutchings@codethink.co.uk>
Subject: Re: [PATCH v3] Renesas Ethernet AVB driver
Date: Fri, 08 May 2015 00:10:36 +0300 [thread overview]
Message-ID: <554BD4CC.3020308@cogentembedded.com> (raw)
In-Reply-To: <553A9123.3010906@cogentembedded.com>
Hello.
On 04/24/2015 09:53 PM, Sergei Shtylyov wrote:
[...]
>>>>> +static int ravb_start_xmit(struct sk_buff *skb, struct net_device
>>>>> *ndev)
>>>>> +{
>>>>> + struct ravb_private *priv = netdev_priv(ndev);
>>>>> + struct ravb_tstamp_skb *ts_skb = NULL;
>>>>> + struct ravb_tx_desc *desc;
>>>>> + unsigned long flags;
>>>>> + void *buffer;
>>>>> + u32 entry;
>>>>> + u32 tccr;
>>>>> + int q;
>>>>> +
>>>>> + /* If skb needs TX timestamp, it is handled in network control
>>>>> queue */
>>>>> + q = (skb_shinfo(skb)->tx_flags & SKBTX_HW_TSTAMP) ? RAVB_NC :
>>>>> RAVB_BE;
>>>>> +
>>>>> + spin_lock_irqsave(&priv->lock, flags);
>>>>> + if (priv->cur_tx[q] - priv->dirty_tx[q] >= priv->num_tx_ring[q]
>>>>> - 4) {
>>>> What's so special about 4 here, you don't seem to be using 4 descriptors
>>> Not sure, this was clearly copied from sh_eth.c. Perhaps it's just a
>>> threshold for calling ravb_tx_free()...
>
>> Then 1 inclusive or 0 exclusive is probably what you should be comparing
>> to, otherwise you may just stop the tx queue earlier than needed.
> Will look into this...
OK, I've fixed this.
[...]
>>>>> + desc->ds = skb->len;
>>>>> + desc->dptr = dma_map_single(&ndev->dev, buffer, skb->len,
>>>>> + DMA_TO_DEVICE);
>>>>> + if (dma_mapping_error(&ndev->dev, desc->dptr)) {
>>>>> + dev_kfree_skb_any(skb);
>>>>> + priv->tx_skb[q][entry] = NULL;
>>>> Don't you need to make sure this NULL is properly seen by ravb_tx_free()?
>>> You mean doing this before releasing the spinlock? Or what?
>> Yes, the locking your transmit function seems to open windows during
>> which it is possible for the interrupt handler running on another CPU to
>> mess up with the data you are using here.
> Will look into that too...
I have looked into the code and I must admit I don't understand how the
data can be messed up with. ravb_tx_free() only advances 'priv->dirty_tx' and
doesn't go beyond (or change) 'priv->cur_tx' which is used here...
>> --
>> Florian
WBR, Sergei
next prev parent reply other threads:[~2015-05-07 21:10 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 22:07 [PATCH v3] Renesas Ethernet AVB driver Sergei Shtylyov
2015-04-13 22:07 ` Sergei Shtylyov
2015-04-13 22:38 ` Florian Fainelli
2015-04-13 22:38 ` Florian Fainelli
2015-04-14 21:37 ` Sergei Shtylyov
2015-04-14 21:37 ` Sergei Shtylyov
2015-04-22 5:04 ` MITSUHIRO KIMURA
2015-04-22 5:04 ` MITSUHIRO KIMURA
2015-04-22 15:36 ` David Miller
2015-04-22 15:36 ` David Miller
2015-04-22 20:30 ` Sergei Shtylyov
2015-04-22 20:30 ` Sergei Shtylyov
2015-04-22 20:42 ` David Miller
2015-04-22 20:42 ` David Miller
2015-04-22 20:46 ` Sergei Shtylyov
2015-04-22 20:46 ` Sergei Shtylyov
2015-04-22 22:17 ` David Miller
2015-04-22 22:17 ` David Miller
2015-04-22 21:38 ` Sergei Shtylyov
2015-04-22 21:38 ` Sergei Shtylyov
2015-04-22 22:18 ` David Miller
2015-04-22 22:18 ` David Miller
2015-04-22 22:34 ` Sergei Shtylyov
2015-04-22 22:34 ` Sergei Shtylyov
2015-04-22 22:41 ` David Miller
2015-04-22 22:41 ` David Miller
2015-04-22 22:50 ` Sergei Shtylyov
2015-04-22 22:50 ` Sergei Shtylyov
2015-04-24 9:03 ` David Laight
2015-04-24 18:27 ` Sergei Shtylyov
2015-04-24 18:27 ` Sergei Shtylyov
2015-04-27 9:22 ` David Laight
2015-04-22 23:22 ` Florian Fainelli
2015-04-22 23:22 ` Florian Fainelli
2015-04-24 18:53 ` Sergei Shtylyov
2015-04-24 18:53 ` Sergei Shtylyov
2015-04-28 17:09 ` Ben Hutchings
2015-04-28 17:09 ` Ben Hutchings
2015-05-07 21:10 ` Sergei Shtylyov [this message]
2015-05-07 21:10 ` Sergei Shtylyov
2015-05-07 21:25 ` Sergei Shtylyov
2015-05-07 21:25 ` Sergei Shtylyov
2015-04-14 0:49 ` Lino Sanfilippo
2015-04-14 0:49 ` Lino Sanfilippo
2015-04-14 11:31 ` David Laight
2015-04-19 22:10 ` Sergei Shtylyov
2015-04-19 22:10 ` Sergei Shtylyov
2015-04-19 23:45 ` Lino Sanfilippo
2015-04-19 23:45 ` Lino Sanfilippo
2015-04-19 9:19 ` Richard Cochran
2015-04-19 9:19 ` Richard Cochran
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=554BD4CC.3020308@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-sh@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mitsuhiro.kimura.kc@renesas.com \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=richardcochran@gmail.com \
--cc=robh+dt@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 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.