From: Janpieter Sollie <janpieter.sollie@telenet.be>
To: linux-kernel@vger.kernel.org
Subject: Re: POI: nvidia forcedeth phy id not present
Date: Fri, 10 Aug 2012 19:08:41 +0200 [thread overview]
Message-ID: <50254019.1030304@telenet.be> (raw)
In-Reply-To: <50244458.5040906@telenet.be>
A primary concern seems to be solved (4k frame size).
However, it is not really a patch yet, just a dirty workaround (just replaced ETH_DATA_LEN with
a value 4000, my switch is limited to 4k)
486c486
< #define NV_PKTLIMIT_1_ETH_DATA_LEN /* hard limit not known */
---
> #define NV_PKTLIMIT_1 4000 /* hard limit not known */
I will try to improve the MTU detection in driver, but it can take some time before I really
understand what each function does. I do not know if this workaround forces a value to the
'initiated' phy, or just forces a wrong MTU to be used on standard nvidia cards.
the results are worth considering: dd -if=//server/share of=/dev/null went from 91 to 112 mbps
(and this is no file cache, the pc has 2gb ram (>50% used by GUI) and the source file is 30 ...)
any help developing a patch may be useful. Is there some documentation about this driver module?
prev parent reply other threads:[~2012-08-10 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50243237.9040704@telenet.be>
2012-08-09 23:14 ` Janpieter Sollie
2012-08-10 17:08 ` Janpieter Sollie [this message]
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=50254019.1030304@telenet.be \
--to=janpieter.sollie@telenet.be \
--cc=linux-kernel@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
Powered by JetHome