From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.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
Subject: Re: [PATCH v3] Renesas Ethernet AVB driver
Date: Mon, 20 Apr 2015 01:45:23 +0200 [thread overview]
Message-ID: <55343E13.9090301@gmx.de> (raw)
In-Reply-To: <553427C9.7030605@cogentembedded.com>
Hi,
On 20.04.2015 00:10, Sergei Shtylyov wrote:
>
>> I recall a thread in which the use of bitfields for structs that are
>> shared with the hardware was considered a bad idea (because the compiler
>> is free to reorder the fields). Shift operations are probably a better
>> choice here.
>
> Well, it looks as the compiler is not free to reorder bit fields, and the
> order is determined by the ABI. Will look into getting rid of them anyway...
I think that thread I was referring to was this one:
http://thread.gmane.org/gmane.linux.kernel/182862/focus=182986
(See the first comment from Benjamin Herrenschmidt).
>>> +/* Packet transmit function for Ethernet AVB */
>>> +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) {
>>> + if (!ravb_tx_free(ndev, q)) {
>>> + netif_warn(priv, tx_queued, ndev, "TX FD exhausted.\n");
>>> + netif_stop_queue(ndev);
>>> + spin_unlock_irqrestore(&priv->lock, flags);
>>> + return NETDEV_TX_BUSY;
>>> + }
>>> + }
>>> + entry = priv->cur_tx[q] % priv->num_tx_ring[q];
>>> + priv->cur_tx[q]++;
>>> + spin_unlock_irqrestore(&priv->lock, flags);
>>> +
>>> + if (skb_put_padto(skb, ETH_ZLEN))
>>> + return NETDEV_TX_OK;
>>> +
>>> + priv->tx_skb[q][entry] = skb;
>>> + buffer = PTR_ALIGN(priv->tx_buffers[q][entry], RAVB_ALIGN);
>>> + memcpy(buffer, skb->data, skb->len);
>>> + desc = &priv->tx_ring[q][entry];
>>> + 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;
>>> + return NETDEV_TX_OK;
>>> + }
>>> +
>>> + /* TX timestamp required */
>>> + if (q == RAVB_NC) {
>>> + ts_skb = kmalloc(sizeof(*ts_skb), GFP_ATOMIC);
>>> + if (!ts_skb)
>>> + return -ENOMEM;
>
>> Dma mapping has to be undone.
>
> OK, fixed. Not sure what we should return in this case: error code or
> NETDEV_TX_OK...
NETDEV_TX_OK is the correct return value even in error case. The only
exception is NETDEV_TX_BUSY when the tx queue has been stopped. However
returning NETDEV_TX_OK also means that the skb has to be consumed (so
beside unmapping dma also the skb has to be freed in case that kmalloc
fails in ravb_start_xmit).
>> example all ptp related code could be put into its own file.
>
> OK, will try to split the driver back... Perhaps I should also split the
> patch accordingly?
Yes, sounds like a good idea.
Regards,
Lino
next prev parent reply other threads:[~2015-04-19 23:45 UTC|newest]
Thread overview: 27+ 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:38 ` Florian Fainelli
2015-04-14 21:37 ` Sergei Shtylyov
2015-04-22 5:04 ` MITSUHIRO KIMURA
2015-04-22 15:36 ` David Miller
2015-04-22 20:30 ` Sergei Shtylyov
2015-04-22 20:42 ` David Miller
2015-04-22 20:46 ` Sergei Shtylyov
2015-04-22 22:17 ` David Miller
2015-04-22 21:38 ` Sergei Shtylyov
2015-04-22 22:18 ` David Miller
2015-04-22 22:34 ` Sergei Shtylyov
2015-04-22 22:41 ` David Miller
2015-04-22 22:50 ` Sergei Shtylyov
2015-04-24 9:03 ` David Laight
2015-04-24 18:27 ` Sergei Shtylyov
2015-04-27 9:22 ` David Laight
2015-04-22 23:22 ` Florian Fainelli
2015-04-24 18:53 ` Sergei Shtylyov
2015-04-28 17:09 ` Ben Hutchings
2015-05-07 21:10 ` Sergei Shtylyov
2015-05-07 21:25 ` Sergei Shtylyov
2015-04-14 0:49 ` Lino Sanfilippo
2015-04-14 11:31 ` David Laight
2015-04-19 22:10 ` Sergei Shtylyov
2015-04-19 23:45 ` Lino Sanfilippo [this message]
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=55343E13.9090301@gmx.de \
--to=linosanfilippo@gmx.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-sh@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).