netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Denys Fedoryshchenko" <denys@visp.net.lb>
To: netdev@vger.kernel.org
Cc: romieu@fr.zoreil.com
Subject: r8169 rx descriptors
Date: Mon, 16 Jun 2008 00:26:48 +0300	[thread overview]
Message-ID: <20080615211030.M80450@visp.net.lb> (raw)

>From NetBSD sources
http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/sys/dev/ic/rtl8169.c?rev=1.14.2.7&content-type=text/plain&logsort=rev&f=h&only_with_tag=netbsd-3

 *      o RX and TX DMA rings can have up to 1024 descriptors
 *        (the 8139C+ allows a maximum of 64)



Why in Linux source:

#define NUM_TX_DESC     64      /* Number of Tx descriptor registers */
#define NUM_RX_DESC     256     /* Number of Rx descriptor registers */

Is it possible to do them changeable over ethtool -g ?
Maybe NetBSD developers signed NDA and have access to datasheets?

Also i seen in one patch from Realtek , something similar to
-#define RX_DMA_BURST    6       /* Maximum PCI burst, '6' is 1024 */
+#define RX_DMA_BURST    7       /* Maximum PCI burst, '6' is 1024 */

Why it is reverted or not applied?


In sources from Realtek website it is 
#define RX_DMA_BURST	7	/* Maximum PCI burst, '7' is unlimited */
#define TX_DMA_BURST	7	/* Maximum PCI burst, '7' is unlimited */

I will try to change burst settings on my router, and waiting comments about 

--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.


             reply	other threads:[~2008-06-15 21:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-15 21:26 Denys Fedoryshchenko [this message]
2008-06-15 22:04 ` r8169 rx descriptors Francois Romieu
2008-06-16 10:37   ` Denys Fedoryshchenko
2008-06-16 20:34     ` Francois Romieu

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=20080615211030.M80450@visp.net.lb \
    --to=denys@visp.net.lb \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    /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;
as well as URLs for NNTP newsgroup(s).