From: Bruce Richardson <bruce.richardson@intel.com>
To: Zhe Tao <zhe.tao@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] ixgbe: fix ixgbevf RX/TX function assignment
Date: Thu, 10 Mar 2016 15:20:06 +0000 [thread overview]
Message-ID: <20160310152005.GG18264@bricha3-MOBL3> (raw)
In-Reply-To: <1457426981-22571-1-git-send-email-zhe.tao@intel.com>
On Tue, Mar 08, 2016 at 04:49:41PM +0800, Zhe Tao wrote:
> For the secondary process of DPDK to initialize ixgbevf, it will always
> use the simple RX function or LRO RX function, and this behavior is not
> the same RX/TX function selection logic as it is for the primary process,
> so use the ixgbe_set_tx_function and ixgbe_set_rx_function to select the
> RX/TX function when secondary process call the init function for eth dev.
>
> Fixes: abf7275bbaa2918 (ixgbe: move to drivers/net/)
That doesn't look to be the commit that actually introduced the bug.
>
> V2:add fixes line
>
> Signed-off-by: Zhe Tao <zhe.tao@intel.com>
>
Checkpatch flags two minor issues with this:
CHECK:SPACING: spaces preferred around that '-' (ctx:VxV)
#33: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:1299:
+ txq = eth_dev->data->tx_queues[eth_dev->data->nb_tx_queues-1];
^
WARNING:SPLIT_STRING: quoted string split across lines
#38: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:1304:
+ PMD_INIT_LOG(NOTICE, "No TX queues configured yet. "
+ "Using default TX function.");
total: 0 errors, 1 warnings, 1 checks, 23 lines checked
/Bruce
next prev parent reply other threads:[~2016-03-10 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 15:07 [dpdk-dev] [PATCH] " Zhe Tao
2016-03-04 5:30 ` Wu, Jingjing
2016-03-08 8:49 ` [dpdk-dev] [PATCH v2] " Zhe Tao
2016-03-10 15:20 ` Bruce Richardson [this message]
2016-03-10 15:26 ` [dpdk-dev] [PATCH v3] " Bruce Richardson
2016-03-10 15:29 ` Zhang, Helin
2016-03-10 15:33 ` Bruce Richardson
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=20160310152005.GG18264@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=zhe.tao@intel.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).