netdev - Re: DMA allocation driver defined limit?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 25 Apr 2013 23:15:16 +0200
From:	Javier Domingo <javierdo1@...il.com>
To:	Ben Hutchings <bhutchings@...arflare.com>
Cc:	netdev@...r.kernel.org
Subject: Re: DMA allocation driver defined limit?

> 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).

So the limit is on number of skbuff nuber and it is self-imposed by the card.

> 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.

I have found that the limit on rings is consistent, as it only
allocates another area when the later one is unmapped.

One last question is: If netdev_budget is 300, why the DMA ring size
is 256 by default in e1000? Shouldn't it be greater than 300, so that
if it has enought packets in one softirq, it could capture them?

Thanks a lot for the reply,

Javier Domingo
--
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