From: David Miller <davem@davemloft.net>
To: Ramkrishna.Vepa@neterion.com
Cc: mschmidt@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH] vxge: fix GRO receive with INTA interrupts
Date: Fri, 26 Jun 2009 00:47:44 -0700 (PDT) [thread overview]
Message-ID: <20090626.004744.100591404.davem@davemloft.net> (raw)
In-Reply-To: <78C9135A3D2ECE4B8162EBDCE82CAD77056E4779@nekter>
From: "Ramkrishna Vepa" <Ramkrishna.Vepa@neterion.com>
Date: Thu, 25 Jun 2009 17:18:19 -0400
> Thanks. We are in the midst of submitting a few bug fixes and will add
> this fix to the list. We fixed it without assuming that only 1 vpath
> will be enabled with INTA. It's been hard coded to 1 with INTA, for
> performance reasons, but when I get some time, I'd like to optimize the
> completion handling to over come this issue.
Since you say you'll integrate into your fix pile I'll wait for
that.
prev parent reply other threads:[~2009-06-26 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 16:31 [PATCH] vxge: fix GRO receive with INTA interrupts Michal Schmidt
2009-06-25 21:18 ` Ramkrishna Vepa
2009-06-26 7:47 ` David Miller [this message]
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=20090626.004744.100591404.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Ramkrishna.Vepa@neterion.com \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).