public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
	David Miller <davem@davemloft.net>,
	luis.henriques@canonical.com, netdev@vger.kernel.org,
	jcliburn@gmail.com, stable@vger.kernel.org
Subject: Re: [net PATCH] atl1c: Fix misuse of netdev_alloc_skb in refilling rx ring
Date: Sun, 28 Jul 2013 16:20:54 -0700	[thread overview]
Message-ID: <1375053654.3669.58.camel@edumazet-glaptop> (raw)
In-Reply-To: <1375052482.3669.54.camel@edumazet-glaptop>

On Sun, 2013-07-28 at 16:01 -0700, Eric Dumazet wrote:
> On Sun, 2013-07-28 at 21:22 +0100, Ben Hutchings wrote:
> 
> > 
> > Since we know lengths > 4K work, perhaps it would be worth testing with
> > the fragment cache size reduced to 16K?  The driver would never
> > previously have used RX buffers crossing 16K boundaries, except if SLOB
> > was used (and that's an unlikely combination).
> 
> Sure, please note the following maths :
> 
> NET_SKB_PAD + 1536 + sizeof(struct skb_shared_info) = 1920
> 
> 16384/1920 = 8
> 
> 32768/1920 = 17
> 
> I don't think atl1c is used in any critical host (given it doesn't even
> provide RX checksums and GRO ...), so I will provide a patch doing mere
> page allocations.
> 

Oh well, look at code around line 2530

        * The atl1c chip can DMA to 64-bit addresses, but it uses a single
         * shared register for the high 32 bits, so only a single, aligned,
         * 4 GB physical address range can be used at a time.
         *
         * Supporting 64-bit DMA on this hardware is more trouble than it's
         * worth.  It is far easier to limit to 32-bit DMA than update
         * various kernel subsystems to support the mechanics required by a
         * fixed-high-32-bit system.
         */
        if ((pci_set_dma_mask(pdev, DMA_BIT_MASK(32)) != 0) ||
            (pci_set_consistent_dma_mask(pdev, DMA_BIT_MASK(32)) != 0)) {
                dev_err(&pdev->dev, "No usable DMA configuration,aborting\n");
                goto err_dma;
        }

It looks like we have a winner !

This $@!? really needs DMA32 allocations.

Currently only tested on TX patch, it needs same care on RX

diff --git a/drivers/net/ethernet/atheros/atl1c/atl1c_main.c b/drivers/net/ethernet/atheros/atl1c/atl1c_main.c
index 786a874..e2ee962 100644
--- a/drivers/net/ethernet/atheros/atl1c/atl1c_main.c
+++ b/drivers/net/ethernet/atheros/atl1c/atl1c_main.c
@@ -1660,7 +1660,8 @@ static int atl1c_alloc_rx_buffer(struct atl1c_adapter *adapter)
 	while (next_info->flags & ATL1C_BUFFER_FREE) {
 		rfd_desc = ATL1C_RFD_DESC(rfd_ring, rfd_next_to_use);
 
-		skb = netdev_alloc_skb(adapter->netdev, adapter->rx_buffer_len);
+		skb = __netdev_alloc_skb(adapter->netdev, adapter->rx_buffer_len,
+					 GFP_ATOMIC | GFP_DMA32);
 		if (unlikely(!skb)) {
 			if (netif_msg_rx_err(adapter))
 				dev_warn(&pdev->dev, "alloc rx buffer failed\n");

  reply	other threads:[~2013-07-28 23:20 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 16:47 [net PATCH] atl1c: Fix misuse of netdev_alloc_skb in refilling rx ring Neil Horman
2013-07-26 16:56 ` Luis Henriques
2013-07-26 17:02   ` Neil Horman
2013-07-26 22:56     ` David Miller
2013-07-27 16:25       ` Luis Henriques
2013-07-27  0:02 ` Ben Hutchings
2013-07-27  0:24   ` Ben Hutchings
2013-07-27 19:30     ` Luis Henriques
2013-07-27 19:49       ` Eric Dumazet
2013-07-27 21:30       ` Ben Hutchings
2013-07-27 23:59         ` Eric Dumazet
2013-07-28  3:02           ` David Miller
2013-07-28 10:44             ` Neil Horman
2013-07-28 16:15               ` Eric Dumazet
2013-07-28 18:53                 ` Neil Horman
2013-07-28 19:21                   ` Eric Dumazet
2013-07-28 20:08                     ` Eric Dumazet
2013-07-28 20:22                   ` Ben Hutchings
2013-07-28 23:01                     ` Eric Dumazet
2013-07-28 23:20                       ` Eric Dumazet [this message]
2013-07-28 23:25                         ` Eric Dumazet
2013-07-28 23:38                         ` Neil Horman
2013-07-29  0:07                         ` Ben Hutchings
2013-07-29  0:21                           ` David Miller
2013-07-29  0:26                           ` Eric Dumazet
2013-07-29  9:55                         ` Luis Henriques
2013-07-29 10:57                           ` Eric Dumazet
2013-07-29 12:09                             ` Luis Henriques
2013-07-29 15:30                               ` Eric Dumazet
2013-07-29 17:24                                 ` Eric Dumazet
2013-07-30  8:53                                   ` Luis Henriques
2013-07-31  2:11                                   ` David Miller
2013-07-31 17:48                                     ` Benjamin Poirier
2013-07-31 17:56                                       ` Eric Dumazet
2013-07-31 19:01                                       ` David Miller
2013-08-01  1:57                                         ` Eric Dumazet

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=1375053654.3669.58.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=jcliburn@gmail.com \
    --cc=luis.henriques@canonical.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=stable@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