netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Willem de Bruijn <willemb@google.com>
Cc: rdunlap@xenotime.net, linux-doc@vger.kernel.org,
	davem@davemloft.net, netdev@vger.kernel.org, therbert@google.com
Subject: Re: [PATCH 2/2] net: minor update to Documentation/networking/scaling.txt
Date: Fri, 12 Aug 2011 16:32:32 -0700	[thread overview]
Message-ID: <4E45B810.3000501@hp.com> (raw)
In-Reply-To: <4E4476CC.5050900@google.com>

On 08/11/2011 05:41 PM, Willem de Bruijn wrote:
> Incorporate last comments about hyperthreading, interrupt coalescing and
> the definition of cache domains into the network scaling document scaling.txt
>
> Signed-off-by: Willem de Bruijn<willemb@google.com>
>
> ---
>   Documentation/networking/scaling.txt |   23 +++++++++++++++--------
>   1 files changed, 15 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/networking/scaling.txt b/Documentation/networking/scaling.txt
> index 3da03c3..6197126 100644
> --- a/Documentation/networking/scaling.txt
> +++ b/Documentation/networking/scaling.txt
> @@ -52,7 +52,8 @@ module parameter for specifying the number of hardware queues to
>   configure. In the bnx2x driver, for instance, this parameter is called
>   num_queues. A typical RSS configuration would be to have one receive queue
>   for each CPU if the device supports enough queues, or otherwise at least
> -one for each cache domain at a particular cache level (L1, L2, etc.).
> +one for each memory domain, where a memory domain is a set of CPUs that
> +share a particular memory level (L1, L2, NUMA node, etc.).

I'd suggest simply "share a particular level in the memory hierarchy 
(Cache, NUMA node, etc)"  and that way you get away from people asking 
nitpicky questions about where cache hierarchy counting starts, and at 
what level caches might be shared :)

Apart from that, looks fine.

rick jones

  reply	other threads:[~2011-08-12 23:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 14:20 [PATCH v2] net: add Documentation/networking/scaling.txt Willem de Bruijn
2011-08-09 18:45 ` Rick Jones
2011-08-11 14:26   ` Will de Bruijn
2011-08-11 16:31     ` Eric Dumazet
2011-08-11 18:02       ` Rick Jones
2011-08-11 21:34         ` Will de Bruijn
2011-08-12  0:34   ` [PATCH 00/02] small changes to Documentation/networking/00-INDEX and scaling.txt Willem de Bruijn
2011-08-12  0:39     ` [PATCH 01/02] net: add missing entries to Documentation/networking/00-INDEX Willem de Bruijn
2011-08-12  7:40       ` Michał Mirosław
2011-08-12  0:41     ` [PATCH 2/2] net: minor update to Documentation/networking/scaling.txt Willem de Bruijn
2011-08-12 23:32       ` Rick Jones [this message]
2011-08-15 16:11         ` Will de Bruijn
2011-08-15 16:56           ` Rick Jones
2011-08-14  1:03     ` [PATCH 00/02] small changes to Documentation/networking/00-INDEX and scaling.txt David Miller
2011-08-10 14:57 ` [PATCH v2] net: add Documentation/networking/scaling.txt David Miller

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=4E45B810.3000501@hp.com \
    --to=rick.jones2@hp.com \
    --cc=davem@davemloft.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=therbert@google.com \
    --cc=willemb@google.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).