Hi Dave,
I just had some time to investigate your comment, and run the script you
linked to, and indeed there may be some problem here. The output of the
script is shown below, which seems to indicate that all of the NICs are
connected to cpus 0-7 (socket 0). We steered the interrupts (47 and
Hi Dave,
When you say multi-socket, do you mean multi-processor? There are two 16 core
AMD Opteron processors. We are using taskset, and have tried every permutation
we could think of. I’ll check out the script.
Thanks,
Dale
Sent from my iPhone
> On Oct 3, 2018, at 9:39 PM, David
HI, Dale,
Is this a multi-socket system? If so, are you using "numactl" or "taskset" to
bind the packet reading processes to CPU(s) on the same socket that the NIC is
connected to? Are you sure you are sending the NIC interrupts to CPU(s) on the
socket that the NIC is connected to?
FWIW,
Hi All,
I thought I would send an update to this problem, which still persists.
Jonathan's suggestion did not seem to work, since each ethernet interface
does not send packets to multiple processors. If I specify two cpus in the
SMP_AFFINITY files, the board sends to only one of them. Also, I
First sorry for the delay, I was off for a time.
We do not use UBUNTU, but DEBIAN, but the two distribs are in fact two
flavours ofthe same thing.
We manage on each machine an UDP download link from a ROACH2. ROACH2
does nothing but adding an 8byte counter to each 8K data block. That way
Hi All,
We are running a multi-core (32-core) system at Owens Valley that has a
dual-port Myricom 10GBe NIC. We ran the system very successfully under
Ubuntu 12.04 for more than 1 year, but after upgrading to Ubuntu 18.04
(generic) we are now experiencing reliability problems, despite the tuning
6 matches
Mail list logo