From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: mcarlson@broadcom.com, bhutchings@solarflare.com,
john.r.fastabend@intel.com, netdev@vger.kernel.org,
therbert@google.com
Subject: Re: [net-next-2.6 PATCH] net: netif_set_real_num_rx_queues may cap num_rx_queues at init time
Date: Wed, 06 Oct 2010 13:41:16 -0700 (PDT) [thread overview]
Message-ID: <20101006.134116.115942855.davem@davemloft.net> (raw)
In-Reply-To: <1286390945.9417.46.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 06 Oct 2010 20:49:05 +0200
> Le mercredi 06 octobre 2010 à 11:14 -0700, Matt Carlson a écrit :
>
>> Yes. We were missing a call to this function in the legacy case.
>>
>>
>> [PATCH net-next] tg3: Set real_num_rx_queues for non-multiq devs
>>
>> Commit 2ddaad397c47de012dfb956b0c05540da1a0dde5 entitled "tg3: Use
>> netif_set_real_num_{rx,tx}_queues()" added a new call to
>> netif_set_real_num_rx_queues in tg3_enable_msix(). This call also needs
>> to be added to the legacy path to correctly reflect the actual number of
>> rx queues.
>>
>> Signed-off-by: Matt Carlson <mcarlson@broadcom.com>
...
> Acked-by: Eric Dumazet <eric.dumazet@gmail.com>
Applied, thanks everyone.
next prev parent reply other threads:[~2010-10-06 20:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 22:00 [net-next-2.6 PATCH] net: netif_set_real_num_rx_queues may cap num_rx_queues at init time John Fastabend
2010-10-05 5:35 ` Eric Dumazet
2010-10-05 16:08 ` John Fastabend
2010-10-05 16:34 ` Ben Hutchings
2010-10-05 17:45 ` John Fastabend
2010-10-06 14:52 ` John Fastabend
2010-10-06 15:07 ` Ben Hutchings
2010-10-06 15:20 ` John Fastabend
2010-10-06 15:23 ` Eric Dumazet
2010-10-06 15:31 ` Ben Hutchings
2010-10-06 18:14 ` Matt Carlson
2010-10-06 18:49 ` Eric Dumazet
2010-10-06 20:41 ` David Miller [this message]
2010-10-06 15:20 ` Eric Dumazet
2010-10-07 6:16 ` Eric Dumazet
2010-10-07 6:35 ` David Miller
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=20101006.134116.115942855.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=eric.dumazet@gmail.com \
--cc=john.r.fastabend@intel.com \
--cc=mcarlson@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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).