From: David Miller <davem@davemloft.net>
To: dhananjay@netxen.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] netxen: revert jumbo ringsize
Date: Thu, 29 Jan 2009 16:05:27 -0800 (PST) [thread overview]
Message-ID: <20090129.160527.32239609.davem@davemloft.net> (raw)
In-Reply-To: <1233261028-27584-1-git-send-email-dhananjay@netxen.com>
From: Dhananjay Phadke <dhananjay@netxen.com>
Date: Thu, 29 Jan 2009 12:30:28 -0800
> Reducing jumbo ring size below 1024 reduces throughput for old
> firmwares (3.4.216 and older) running on older (NX2031) chip,
> so restore it back to 1024.
>
> This was reduced in commit 32ec803348b4d5f1353e1d7feae30880b8b3e342.
>
> Raising jumbo ring size from 512 to 1024, adds ~4MB per port, but
> there's still big saving because of original patch (~20MB per port).
>
> Signed-off-by: Dhananjay Phadke <dhananjay@netxen.com>
Applied, thanks.
prev parent reply other threads:[~2009-01-30 0:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 20:30 [PATCH] netxen: revert jumbo ringsize Dhananjay Phadke
2009-01-30 0:05 ` David Miller [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=20090129.160527.32239609.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dhananjay@netxen.com \
--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;
as well as URLs for NNTP newsgroup(s).