From: Andi Kleen <andi@firstfloor.org>
To: Ramkrishna Vepa <Ramkrishna.Vepa@neterion.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Sreenivasa Honnur <Sreenivasa.Honnur@neterion.com>,
netdev@vger.kernel.org, jeff@garzik.org,
support <support@neterion.com>
Subject: Re: [PATCH 2.6.25 1/1]S2io: Multiqueue network device support implementation
Date: Thu, 24 Jan 2008 08:25:49 +0100 [thread overview]
Message-ID: <20080124072549.GA6814@one.firstfloor.org> (raw)
In-Reply-To: <78C9135A3D2ECE4B8162EBDCE82CAD7702E70E92@nekter>
> [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
next prev parent reply other threads:[~2008-01-24 6:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 0:45 [PATCH 2.6.25 1/1]S2io: Multiqueue network device support implementation Sreenivasa Honnur
2008-01-23 0:55 ` Jeff Garzik
2008-01-23 10:58 ` Andi Kleen
2008-01-23 20:48 ` Ramkrishna Vepa
2008-01-24 7:25 ` Andi Kleen [this message]
2008-01-24 7:30 ` David Miller
2008-01-25 3:19 ` Ramkrishna Vepa
2008-01-25 3:19 ` Ramkrishna Vepa
-- strict thread matches above, loose matches on Subject: below --
2007-12-26 23:33 Sreenivasa Honnur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080124072549.GA6814@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=Ramkrishna.Vepa@neterion.com \
--cc=Sreenivasa.Honnur@neterion.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=support@neterion.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.