From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2.6.18 3/6] bnx2: Use CPU native page size
Date: Tue, 13 Jun 2006 15:41:13 -0700 (PDT) [thread overview]
Message-ID: <20060613.154113.133441489.davem@davemloft.net> (raw)
In-Reply-To: <1150222782.26368.34.camel@rh4>
From: "Michael Chan" <mchan@broadcom.com>
Date: Tue, 13 Jun 2006 11:19:42 -0700
> Use CPU native page size to determine various ring sizes. This allows
> order-0 memory allocations on all systems.
>
> Added check to limit the page size to 16K since that's the maximum rx
> ring size that will be used. This will prevent using unnecessarily
> large page sizes on some architectures with large page sizes.
> [Suggested by David Miller]
>
> Signed-off-by: Michael Chan <mchan@broadcom.com>
Looks great, applied.
prev parent reply other threads:[~2006-06-13 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 0:17 [PATCH 2.6.18 3/6] bnx2: Use CPU native page size Michael Chan
2006-06-13 5:20 ` David Miller
2006-06-13 18:19 ` Michael Chan
2006-06-13 22:41 ` 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=20060613.154113.133441489.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mchan@broadcom.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).