netdev - Re: NAPI and shared interrupt control

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] [day] [month] [year] [list]

Message-Id: <20061207.235205.102574126.davem@davemloft.net>
Date:	Thu, 07 Dec 2006 23:52:05 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	benh@...nel.crashing.org
Cc:	ebs@...home.net, netdev@...r.kernel.org
Subject: Re: NAPI and shared interrupt control

From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Date: Thu, 07 Dec 2006 21:56:02 +1100

> Dave, the main point of my initial email was: should we provide a
> routine from the net core to initialize such dummy devices properly ?
> I'm a little worried that some day, the NAPI code will change and the
> initialisations done by the driver will not be enough anymore...

That sounds like an excellent idea.

Once you guys have your implementation sorted out, submit
a patch proposing the generic bits and we'll review it.

Thanks.
-
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