From: David Miller <davem@davemloft.net>
To: ptalbert@redhat.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/1] [net] bonding: Add NUMA notice
Date: Sat, 07 Oct 2017 23:20:36 +0100 (WEST) [thread overview]
Message-ID: <20171007.232036.1361815658002685993.davem@davemloft.net> (raw)
In-Reply-To: <1507235025-21689-1-git-send-email-ptalbert@redhat.com>
From: Patrick Talbert <ptalbert@redhat.com>
Date: Thu, 5 Oct 2017 16:23:45 -0400
> Network performance can suffer when a load balancing bond uses slave
> interfaces which are in different NUMA domains.
>
> This compares the NUMA domain of a newly enslaved interface against any
> existing enslaved interfaces and prints a warning if they do not match.
>
> Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
This is a bit over the top, and doesn't even handle cases where
the device has no specific NUMA node (-1).
next prev parent reply other threads:[~2017-10-07 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 20:23 [PATCH net-next 1/1] [net] bonding: Add NUMA notice Patrick Talbert
2017-10-05 21:46 ` Andrew Lunn
2017-10-06 17:54 ` Patrick Talbert
2017-10-06 18:08 ` Eric Dumazet
2017-10-07 22:20 ` David Miller [this message]
2017-10-09 19:00 ` Patrick Talbert
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=20171007.232036.1361815658002685993.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ptalbert@redhat.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).