[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080124072549.GA6814@one.firstfloor.org>
Date: Thu, 24 Jan 2008 08:25:49 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Ramkrishna Vepa <Ramkrishna.Vepa@...erion.com>
Cc: Andi Kleen <andi@...stfloor.org>,
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.
-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
Powered by blists - more mailing lists