netdev - Re: NAPI and TX

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: <20090508.144412.201441401.davem@davemloft.net>
Date:	Fri, 08 May 2009 14:44:12 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	khc@...waw.pl
Cc:	netdev@...r.kernel.org
Subject: Re: NAPI and TX

From: Krzysztof Halasa <khc@...waw.pl>
Date: Fri, 08 May 2009 14:32:25 +0200

> Could NAPI or something similar be used for TX in addition to RX?
> Perhaps some driver already does that?

Many multiqueue drivers do exactly this.  NIU is but one example.

Every discrete event from the chip which can generate discrete
interrupts, uses a unique NAPI context.

If a single interrupt is used to indicate RX and TX, using seperate
NAPI contexts is not advisable.  It's just going to add overhead.
--
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