[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1366828908.2600.4.camel@bwh-desktop.uk.solarflarecom.com>
Date: Wed, 24 Apr 2013 19:41:48 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: Javier Domingo <javierdo1@...il.com>
CC: <netdev@...r.kernel.org>
Subject: Re: DMA allocation driver defined limit?
On Wed, 2013-04-24 at 20:18 +0200, Javier Domingo wrote:
> Hi,
>
> I am trying to find how big can the DMA memory be, as I haven't found
> anything in the docs that describes exactly a general size of DMA
> allocation, I have supposed that it depends entirely on the card.
Right.
> As a general approach, is it alright to suppose that the DMA memory
> will be as big as the internal memory of the network card?
I don't see what the network card's memory has got to do with it. I
would expect that you can allocate and DMA-map much more memory (number
of rings * number of descriptors per ring * maximum length of
descriptor).
> The real question here is, when using DMA, the driver has a limit of
> packet size or a limit of sk_buffs it can receive? For me is like
> there should be a size limit (althought I suppose there can't be
> unlimited skbuffs).
>
> Thanks for your attention and looking back for a replay,
Before you deliver an skb up the stack, you must DMA-unmap the header
area. The stack then takes care of limiting the amount of memory in
use.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
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