Date: Wed, 3 Aug 2016 18:57:28 +0200 From: Ben RUBSON <ben.rubson@gmail.com> To: freebsd-net@freebsd.org Subject: Re: Unstable local network throughput Message-ID: <465615D0-C1CB-42F0-8964-AFAAB5C05E26@gmail.com> In-Reply-To: <bed13ae3-0b8f-b1af-7418-7bf1b9fc74bc@selasky.org> References: <3C0D892F-2BE8-4650-B9FC-93C8EE0443E1@gmail.com> <bed13ae3-0b8f-b1af-7418-7bf1b9fc74bc@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 02 Aug 2016, at 21:35, Hans Petter Selasky <hps@selasky.org> wrote: > > The CX-3 driver doesn't bind the worker threads to specific CPU cores by default, so if your CPU has more than one so-called numa, you'll end up that the bottle-neck is the high-speed link between the CPU cores and not the card. A quick and dirty workaround is to "cpuset" iperf and the interrupt and taskqueue threads to specific CPU cores. Hans Petter, I'm testing "cpuset" and sometimes get better results, I'm still trying to get the best. I've cpuset iperf & Mellanox interrupts, but what do you mean by taskqueue threads ? Thank U ! Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?465615D0-C1CB-42F0-8964-AFAAB5C05E26>