public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Kalpesh Rathod <kalpeshrathod@gmail.com>
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [query] skb alignment in tx path of driver
Date: Thu, 23 Jul 2009 19:16:49 +0200	[thread overview]
Message-ID: <4A689B01.3010007@gmail.com> (raw)
In-Reply-To: <cee4bbc90907230955s558123dpe021fa1e7b384068@mail.gmail.com>

Kalpesh Rathod a écrit :
> Hi,
> 
> I am writing n/w device driver for sdio wifi card. I am testing it on
> embedded platform.
> DMA controller on the platform is able to xfer data to sdio only if
> source data buf address is 4 byte aligned.
> 
> The firmware on the card understands 802.3 frames with snap headers.
> So, I convert it to the required format in my driver.
> 4 byte additional header is also attached to this frame and sent over sdio.
> This all conversion effectively adds 12 byes to the frame received in
> hard_xmit method.
> 
> Problem is, frame received in hard_xmit method is 2 byte aligned.
> (skb->data is 2 byte aligned). As a result,
> after addition of 12 bytes header, skb->data remains 2 byte aligned
> instead of 4 byte aligned. And DMA controller refuses
> to transfer it.
> 
> So, how can I request IP stack so that frame received in hard_xmit is
> on 4 byte aligned boundry?

You cannot.

Search for skb_copy_and_csum_dev() use in drivers.

drivers/net/via-rhine.c is a good example of a driver dealing with same
alignment requirement.

        if ((rp->quirks & rqRhineI) &&
            (((unsigned long)skb->data & 3) || skb_shinfo(skb)->nr_frags != 0 || skb->ip_summed == CHECKSUM_PARTIAL)) {
                /* Must use alignment buffer. */
                if (skb->len > PKT_BUF_SZ) {
                        /* packet too long, drop it */
                        dev_kfree_skb(skb);
                        rp->tx_skbuff[entry] = NULL;
                        dev->stats.tx_dropped++;
                        return NETDEV_TX_OK;
                }

                /* Padding is not copied and so must be redone. */
                skb_copy_and_csum_dev(skb, rp->tx_buf[entry]);
                if (skb->len < ETH_ZLEN)
                        memset(rp->tx_buf[entry] + skb->len, 0,
                               ETH_ZLEN - skb->len);
                rp->tx_skbuff_dma[entry] = 0;
                rp->tx_ring[entry].addr = cpu_to_le32(rp->tx_bufs_dma +
                                                      (rp->tx_buf[entry] -
                                                       rp->tx_bufs));
        } else {
                rp->tx_skbuff_dma[entry] =
                        pci_map_single(rp->pdev, skb->data, skb->len,
                                       PCI_DMA_TODEVICE);
                rp->tx_ring[entry].addr = cpu_to_le32(rp->tx_skbuff_dma[entry]);
        }



  reply	other threads:[~2009-07-23 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23 16:55 [query] skb alignment in tx path of driver Kalpesh Rathod
2009-07-23 17:16 ` Eric Dumazet [this message]
2009-07-23 17:23   ` Stephen Hemminger

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=4A689B01.3010007@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=kalpeshrathod@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@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