[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1FC56210173BB445BD77F608D6FB8D03036AA43501@HQMAIL03.nvidia.com>
Date: Thu, 18 Jun 2009 10:33:43 -0700
From: Ayaz Abdulla <AAbdulla@...dia.com>
To: 'David Miller' <davem@...emloft.net>,
"eric.dumazet@...il.com" <eric.dumazet@...il.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH] forcedeth: fix dma api mismatches
Doing a quick indentifier search on 2.6.17 shows that pci_unmap_page() just calls pci_unmap_single().
I think this will just add extra clutter. We can just add a comment in the code instead that they perform the same thing.
Ayaz
-----Original Message-----
From: David Miller [mailto:davem@...emloft.net]
Sent: Thursday, June 18, 2009 12:47 AM
To: eric.dumazet@...il.com
Cc: Ayaz Abdulla; netdev@...r.kernel.org
Subject: Re: [PATCH] forcedeth: fix dma api mismatches
From: Eric Dumazet <eric.dumazet@...il.com>
Date: Thu, 18 Jun 2009 09:17:59 +0200
> Please find following patch, candidate for stable, but alas not tested
> since I dont have the hardware. I hit this on a 2.6.30 kernel on a machine
> I dont have access anymore.
>
> Thank you
>
> [PATCH] forcedeth: fix dma api mismatches
>
> forcedeth doesnt use properly dma api in its tx completion path
> and in nv_loopback_test()
>
> pci_map_single() should be paired with pci_unmap_single()
> pci_map_page() should be paired with pci_unmap_page()
>
> forcedeth xmit path uses pci_map_single() & pci_map_page(),
> but tx completion path only uses pci_unmap_single()
>
> nv_loopback_test() uses pci_map_single() & pci_unmap_page()
>
> Add a dma_single field in struct nv_skb_map, and
> define a helper function nv_unmap_txskb
>
> Signed-off-by: Eric Dumazet <eric.dumazet@...il.com>
> CC: Ayaz Abdulla <aabdulla@...dia.com>
I'm going to apply this to net-next-2.6 now since it looks
painfully correct to me.
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists