From: David Miller <davem@davemloft.net>
To: therbert@google.com
Cc: netdev@vger.kernel.org
Subject: Re: NUMA and multiQ interation
Date: Tue, 24 Nov 2009 12:10:17 -0800 (PST) [thread overview]
Message-ID: <20091124.121017.231454645.davem@davemloft.net> (raw)
In-Reply-To: <65634d660911241151q4d7522c0nf9c2e4667c333185@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
Date: Tue, 24 Nov 2009 11:51:39 -0800
> I saw that thread, and it looks compelling. But we have applications
> that are network bound such that we want to use multiple queues across
> multiple nodes for scaling-- and trying keep all queues on the same
> node does not scale very well. Maybe ignoring NUMA allocation could
> be a fall-back mode in a dynamic allocation with heavy load?
You use the word "But" as if what PJ and friends are doing is different
from what you're trying to achive. I think they are the same.
prev parent reply other threads:[~2009-11-24 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 17:04 NUMA and multiQ interation Tom Herbert
2009-11-24 17:36 ` Eric Dumazet
2009-11-24 18:06 ` David Miller
2009-11-24 19:51 ` Tom Herbert
2009-11-24 20:10 ` 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=20091124.121017.231454645.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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).