netdev - RE: [PATCH 2.6.25 1/1]S2io: Multiqueue network device support implementation

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: <78C9135A3D2ECE4B8162EBDCE82CAD7702E713B1@nekter>
Date:	Thu, 24 Jan 2008 22:19:45 -0500
From:	"Ramkrishna Vepa" <Ramkrishna.Vepa@...erion.com>
To:	"Andi Kleen" <andi@...stfloor.org>
Cc:	"Sreenivasa Honnur" <Sreenivasa.Honnur@...erion.com>,
	<netdev@...r.kernel.org>, <jeff@...zik.org>,
	"support" <support@...erion.com>
Subject: RE: [PATCH 2.6.25 1/1]S2io: Multiqueue network device support implementation

> > [Ram] I am assuming that this is with regards to msi-x interrupts.
We
> 
> Yes.
> 
> And avoiding bouncing locks for device state between CPUs.
> 
> > have done away with handling tx completion in the interrupt handler,
and
> > are instead handling them in the context of the transmit. The slow
path,
> > straggling transmit completions will be handled in the timer
context.
> 
> Ok -- hopefully you don't have bad corner cases from this when the
pipe
> is not fully filled and then causing longer latencies on completion.
> Old NAPI sometimes suffered from such problems.
[Ram] We have hit the driver pretty hard during testing and have not
encountered any problems either on the network or host.

Ram
> 
> -Andi
--
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