linux-kernel - Re: UDP packets loss

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061114152341.24861967@freekitty>
Date:	Tue, 14 Nov 2006 15:23:41 -0800
From:	Stephen Hemminger <shemminger@...l.org>
To:	eli@....mellanox.co.il
Cc:	eli@....mellanox.co.il, linux-kernel@...r.kernel.org,
	linux-net@...r.kernel.org
Subject: Re: UDP packets loss

On Wed, 15 Nov 2006 01:08:41 +0200 (IST)
eli@....mellanox.co.il wrote:

> Thanks for the commets.
> I actually use UDP because I am seeking for ways to improve the
> performance of IPOIB and I wanted to avoid TCP's flow control. I am really
> up to making anaysis. Can you tell me more about irqbalnced?

Look for info on irqbalance (depends which linux distribution you
are using). You might not be running it at all, and it is completely
optional. There is also a kernel level IRQ balancer that may or
may not be configured.

> Where can I
> find more info how to control it? 

man irqbalance

Note: irqbalance has heuristics about device names and driver names,
it might be worthwhile to either update the source and teach it about
infiniband, or work with existing heuristics (ie. call your interrupt "eth0", "eth1",...)

>I would like my interrupts serviced by
> all CPUs in a somehow equal manner. I mentioned MSIX - the driver already
> make use of MSIX and I thought this is relevant to interrupts affinity.

MSIX is not directly related to affinity. But with MSIX you can have multiple
CPU's all working at once. The device needs to return some info, and the driver
has to register multiple times.

Regular round-robin of network IRQ's is cache hostile, and that is why
irqbalance tries to keep them on the same processor.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/