From: Will de Bruijn <willemb@google.com>
To: Rick Jones <rick.jones2@hp.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: Mon, 15 Aug 2011 12:11:00 -0400 [thread overview]
Message-ID: <CA+FuTScsrN5=NLeHgyNP+TXL+_auU6p80Lb5JUaMb_o5aGGqww@mail.gmail.com> (raw)
In-Reply-To: <4E45B810.3000501@hp.com>
> 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.
Thanks. It is already applied, so if you don't feel strongly about
this, I'll leave it as is (and take any nitpicky flak if that comes ;)
next prev parent reply other threads:[~2011-08-15 16:11 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
2011-08-15 16:11 ` Will de Bruijn [this message]
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='CA+FuTScsrN5=NLeHgyNP+TXL+_auU6p80Lb5JUaMb_o5aGGqww@mail.gmail.com' \
--to=willemb@google.com \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rick.jones2@hp.com \
--cc=therbert@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).