From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Anton Blanchard <anton@samba.org>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Bruce Allan <bruce.w.allan@intel.com>,
PJ Waskiewicz <peter.p.waskiewicz.jr@intel.com>,
John Ronciak <john.ronciak@intel.com>,
Don Skidmore <donald.c.skidmore@intel.com>,
Yi Zou <yi.zou@intel.com>,
Alexander Duyck <alexander.h.duyck@intel.com>,
e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] e1000: Fix DMA mapping error handling on RX
Date: Fri, 22 Jan 2010 19:42:49 -0800 [thread overview]
Message-ID: <9929d2391001221942i65143cdfq9b5c6ff3258d099e@mail.gmail.com> (raw)
In-Reply-To: <20100121114420.GA11892@kryten>
On Thu, Jan 21, 2010 at 03:44, Anton Blanchard <anton@samba.org> wrote:
>
> Check for error return from pci_map_single/pci_map_page and clean up.
>
> With this and the previous patch the driver was able to handle a significant
> percentage of errors (I set the fault injection rate to 10% and could still
> download large files at a reasonable speed).
>
> Signed-off-by: Anton Blanchard <anton@samba.org>
> ---
>
> I wasn't able to stress the jumbo frame path, so that part could do with some
> more eyes.
>
> Index: linux.trees.git/drivers/net/e1000/e1000_main.c
> ===================================================================
> --- linux.trees.git.orig/drivers/net/e1000/e1000_main.c 2010-01-21 11:13:10.000000000 +1100
> +++ linux.trees.git/drivers/net/e1000/e1000_main.c 2010-01-21 11:15:54.000000000 +1100
> @@ -4014,11 +4014,21 @@ check_page:
> }
> }
>
> - if (!buffer_info->dma)
> + if (!buffer_info->dma) {
> buffer_info->dma = pci_map_page(pdev,
> buffer_info->page, 0,
> buffer_info->length,
> PCI_DMA_FROMDEVICE);
> + if (pci_dma_mapping_error(pdev, buffer_info->dma)) {
> + put_page(buffer_info->page);
> + dev_kfree_skb(skb);
> + buffer_info->page = NULL;
> + buffer_info->skb = NULL;
> + buffer_info->dma = 0;
> + adapter->alloc_rx_buff_failed++;
> + break; /* while !buffer_info->skb */
> + }
> + }
>
> rx_desc = E1000_RX_DESC(*rx_ring, i);
> rx_desc->buffer_addr = cpu_to_le64(buffer_info->dma);
> @@ -4109,6 +4119,13 @@ map_skb:
> skb->data,
> buffer_info->length,
> PCI_DMA_FROMDEVICE);
> + if (pci_dma_mapping_error(pdev, buffer_info->dma)) {
> + dev_kfree_skb(skb);
> + buffer_info->skb = NULL;
> + buffer_info->dma = 0;
> + adapter->alloc_rx_buff_failed++;
> + break; /* while !buffer_info->skb */
> + }
>
> /*
> * XXX if it was allocated cleanly it will never map to a
I have added this patch to my queue of patches for review and testing. Thanks.
--
Cheers,
Jeff
next prev parent reply other threads:[~2010-01-23 3:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 11:42 [PATCH 1/2] e1000: Fix DMA mapping error handling on TX Anton Blanchard
2010-01-21 11:44 ` [PATCH 2/2] e1000: Fix DMA mapping error handling on RX Anton Blanchard
2010-01-23 3:42 ` Jeff Kirsher [this message]
2010-01-23 3:40 ` [PATCH 1/2] e1000: Fix DMA mapping error handling on TX Jeff Kirsher
2010-01-24 0:47 ` Anton Blanchard
2010-01-24 3:58 ` Jeff Kirsher
2010-01-26 15:59 ` Roel Kluin
2010-02-04 13:00 ` Roel Kluin
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=9929d2391001221942i65143cdfq9b5c6ff3258d099e@mail.gmail.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=anton@samba.org \
--cc=bruce.w.allan@intel.com \
--cc=donald.c.skidmore@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=yi.zou@intel.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).