From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Tom Barbette <tom.barbette@ulg.ac.be>
Subject: Re: [PATCH] ethernet api: Document rte_eth_vmdq_rx_conf
Date: Thu, 08 Jun 2017 22:48:42 +0200 [thread overview]
Message-ID: <4818076.qqcqROevOE@xps> (raw)
In-Reply-To: <20170511082800.17608-1-tom.barbette@ulg.ac.be>
11/05/2017 10:28, Tom Barbette:
> From documentation it is very unclear how VMDq configuration can be
> tweaked, and online search offer very poor results.
>
> This patch will ultimately spawn an online documentation page
> for the rte_eth_vmdq_rx_conf struct which will eventually add a bit of
> documentation about the rx_mode tag and how to allow e.g. VMDq pools
> to receive packets without VLAN tags.
> ---
I'm not an expert of VMDq.
Please help reviewing this doc addition.
[..]
> +/**
> + * A structure used to configure the VMDQ feature of an Ethernet port when
> + * not combined with the DCB feature.
> + *
> + * Using this feature, packets are routed to a pool of queues. By default, the
> + * pool selection is based on the MAC address, the vlan id in the vlan tag as
> + * specified in the pool_map array.
> + * Passing the ETH_VMDQ_ACCEPT_UNTAGGED in the rx_mode field allows pool
> + * selection using only the MAC address. MAC address to pool mapping is done
> + * using the rte_eth_dev_mac_addr_add function, with the pool parameter
> + * corresponding to the pool id.
> + *
> + * Queue selection within the selected pool will be done using RSS when
> + * it is enabled or revert to the first queue of the pool if not.
> + *
> + * A default pool may be used, if desired, to route all traffic which
> + * does not match the vlan filter rules or any pool MAC address.
> + */
> struct rte_eth_vmdq_rx_conf {
next prev parent reply other threads:[~2017-06-08 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 8:28 [PATCH] ethernet api: Document rte_eth_vmdq_rx_conf Tom Barbette
2017-06-08 20:48 ` Thomas Monjalon [this message]
2017-06-30 14:42 ` Mcnamara, John
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=4818076.qqcqROevOE@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=tom.barbette@ulg.ac.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.