netdev - solutions for forcedeth jumbo rx and order:2 alloc?

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>] [day] [month] [year] [list]

Message-ID: <1261158742.4932.190.camel@ragnarok>
Date:	Fri, 18 Dec 2009 12:52:22 -0500
From:	Jeremy Jackson <jerj@...lanar.net>
To:	netdev@...r.kernel.org
Subject: solutions for forcedeth jumbo rx and order:2 alloc?

Currently, forcedeth seems to want an order:2 alloc for each frame rx.
I find this behaviour makes using 9100 byte jumbos somewhat suicidal O.o
Frequent kernel messages, failure of bridge STP (the goggles, they do
nothing!) due to missed packets, etc.

I realize that it's a reverse engineered driver, and that changing the
way hardware descriptors works to use paged SKBs might be very
difficult, so I'm wondering if the following would work:

Allocate linear static buffers for use in rx ring descriptors once at
device init time (ifconfig up), and copy into paged skbs when handing >
page sized SKBs up to higher layer network stack?  (hmm did i just ask
to copy every rx packet?)

-- 
Jeremy Jackson
Coplanar Networks
(519)489-4903
http://www.coplanar.net
jerj@...lanar.net

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