netdev - Re: [PATCH RFC]: napi

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: <20070728.223339.85409302.davem@davemloft.net>
Date:	Sat, 28 Jul 2007 22:33:39 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jeff@...zik.org
Cc:	shemminger@...ux-foundation.org, netdev@...r.kernel.org,
	hadi@...erus.ca, rusty@...tcorp.com.au
Subject: Re: [PATCH RFC]: napi_struct V4

From: Jeff Garzik <jeff@...zik.org>
Date: Sat, 28 Jul 2007 14:08:44 -0400

> That's a performance/parallelization regression from current NAPI :(

That's not true since current NAPI will only run on one cpu, the
one that the interrupt triggers on.

The existing cases that are not guarding the sequence to be
atomic are racy, and in a way which is very hard to debug when
it triggers and the device just appears dead.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html