linux-kernel - Re: [PATCH net-next v1 0/6] tg3: adaptive interrupt coalescing, non-napi mode

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: <20111216.134247.1388025459559232416.davem@davemloft.net>
Date:	Fri, 16 Dec 2011 13:42:47 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	decot@...glers.com
Cc:	mcarlson@...adcom.com, mchan@...adcom.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, martinez.javier@...il.com,
	rgetz@...ckfin.uclinux.org, mpm@...enic.com
Subject: Re: [PATCH net-next v1 0/6] tg3: adaptive interrupt coalescing,
 non-napi mode

From: David Decotigny <decot@...glers.com>
Date: Fri, 16 Dec 2011 10:19:43 -0800

> This series implements adaptive interrupt coalescing for tg3 NIC,
> improving performance substancially. It also implements non-NAPI mode
> for specific system loads.

I specifically removed the dynamic IRQ coalescing from this driver years
ago.

It's too susceptible to state changes.

I am sure that you have some nice benchmark for which one scheme helps,
but more generally it is not possible to make it such that you will avoid
the case where the network flow pattern changes by the time you change
the chip configuration and thus the result is suboptimal.

I highly recommend these changes are not applied, because they will hurt
someone.
--
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/