Netdev List
 help / color / mirror / Atom feed
From: Jeremy Jackson <jerj@coplanar.net>
To: netdev@vger.kernel.org
Subject: solutions for forcedeth jumbo rx and order:2 alloc?
Date: Fri, 18 Dec 2009 12:52:22 -0500	[thread overview]
Message-ID: <1261158742.4932.190.camel@ragnarok> (raw)

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@coplanar.net


                 reply	other threads:[~2009-12-18 18:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1261158742.4932.190.camel@ragnarok \
    --to=jerj@coplanar.net \
    --cc=netdev@vger.kernel.org \
    /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