From: David Miller <davem@davemloft.net>
To: vkolluri@cisco.com
Cc: netdev@vger.kernel.org
Subject: Re: [net-next-2.6 PATCH 3/3] enic: Always use single transmit and single receive hardware queues per device
Date: Thu, 17 Feb 2011 14:48:21 -0800 (PST) [thread overview]
Message-ID: <20110217.144821.70213322.davem@davemloft.net> (raw)
In-Reply-To: <212AA327A3557741A058E787E06188730564B99A@xmb-sjc-219.amer.cisco.com>
From: "Vasanthy Kolluri (vkolluri)" <vkolluri@cisco.com>
Date: Thu, 17 Feb 2011 14:45:56 -0800
> Sorry for the short description.
>
> We believe that our earlier patch for supporting multiple hardware
> receive queues per enic device requires more internal testing. At this
> point, we think that it's best to disable the use of multiple receive
> queues. We believe that the current patch will provide an effective
> means for the same.
Well then, resubmit your patch with an appropriate commit message.
prev parent reply other threads:[~2011-02-17 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 18:53 [net-next-2.6 PATCH 0/3] enic: updates to version 2.1.1.9 Vasanthy Kolluri
2011-02-17 18:53 ` [net-next-2.6 PATCH 1/3] enic: Bug fix: Reset driver count of registered unicast addresses to zero during device reset Vasanthy Kolluri
2011-02-17 22:14 ` David Miller
2011-02-17 18:53 ` [net-next-2.6 PATCH 2/3] enic: Clean up: Remove a not needed #ifdef Vasanthy Kolluri
2011-02-17 22:14 ` David Miller
2011-02-17 18:53 ` [net-next-2.6 PATCH 3/3] enic: Always use single transmit and single receive hardware queues per device Vasanthy Kolluri
2011-02-17 22:12 ` David Miller
2011-02-17 22:45 ` Vasanthy Kolluri (vkolluri)
2011-02-17 22:48 ` 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=20110217.144821.70213322.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vkolluri@cisco.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 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).