From: Michal Jastrzebski <michalx.k.jastrzebski@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v3 0/2] testpmd: check return value of rte_eth_dev_vlan_filter()
Date: Fri, 20 Feb 2015 11:26:10 +0100 [thread overview]
Message-ID: <1424427972-6392-1-git-send-email-michalx.k.jastrzebski@intel.com> (raw)
In-Reply-To: <1422379175-10004-1-git-send-email-michalx.k.jastrzebski@intel.com>
v3 changes:
- add seperate patch with testpmd_funcs.rst changes
v2 changes:
- fix formatting errors
This patchset modifies testpmd behavior when setting:
rx_vlan add all vf_port (enabling all vlanids
to be passed thru rx filter on VF).
Rx_vlan_all_filter_set() function,
checks if the next vlanid can be enabled by the driver.
Number of vlanids is limited by the NIC and thus the NIC
do not allow to enable more vlanids than it can allocate
in VFTA table.
tespmd_funcs.rst file is modified to provide a brief description
why enabling all vlan ids may not be possible.
Michal Jastrzebski (2):
doc: add information about limited number of vlan_ids
testpmd: check return value of rte_eth_dev_vlan_filter()
app/test-pmd/config.c | 15 +++++++++------
app/test-pmd/testpmd.h | 2 +-
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 2 ++
lib/librte_ether/rte_ethdev.c | 4 ++--
4 files changed, 14 insertions(+), 9 deletions(-)
--
1.7.9.5
next prev parent reply other threads:[~2015-02-20 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 17:19 [dpdk-dev] [PATCH v2] testpmd " Michal Jastrzebski
2015-01-28 1:38 ` Qiu, Michael
2015-02-20 9:08 ` Jastrzebski, MichalX K
2015-02-20 10:26 ` Michal Jastrzebski [this message]
2015-02-20 10:26 ` [dpdk-dev] [PATCH v3 1/2] doc: add information about limited number of vlan_ids Michal Jastrzebski
2015-02-20 10:26 ` [dpdk-dev] [PATCH v3 2/2] testpmd: check return value of rte_eth_dev_vlan_filter() Michal Jastrzebski
2015-03-07 21:28 ` [dpdk-dev] [PATCH v3 0/2] " De Lara Guarch, Pablo
2015-03-09 11:00 ` Thomas Monjalon
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=1424427972-6392-1-git-send-email-michalx.k.jastrzebski@intel.com \
--to=michalx.k.jastrzebski@intel.com \
--cc=dev@dpdk.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).