From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH 1/6] ether: enhancement for VMDQ support Date: Tue, 14 Oct 2014 16:09:36 +0200 Message-ID: <20784375.UWMeVtoV91@xps13> References: <1411478047-1251-1-git-send-email-jing.d.chen@intel.com> <1411478047-1251-2-git-send-email-jing.d.chen@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev-VfR2kkLFssw@public.gmane.org To: "Chen Jing D(Mark)" Return-path: In-Reply-To: <1411478047-1251-2-git-send-email-jing.d.chen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 2014-09-23 21:14, Chen Jing D: > The change includes several parts: > 1. Clear pool bitmap when trying to remove specific MAC. > 2. Define RSS, DCB and VMDQ flags to combine rx_mq_mode. > 3. Use 'struct' to replace 'union', which to expand the rx_adv_conf > arguments to better support RSS, DCB and VMDQ. > 4. Fix bug in rte_eth_dev_config_restore function, which will restore > all MAC address to default pool. > 5. Define additional 3 arguments for better VMDQ support. > > Signed-off-by: Chen Jing D(Mark) > Acked-by: Konstantin Ananyev > Acked-by: Jingjing Wu > Acked-by: Jijiang Liu > Acked-by: Huawei Xie Whaou, there were a lot of reviewers! The patch should be really clean. Let's see :) > --- a/lib/librte_ether/rte_ethdev.c > +++ b/lib/librte_ether/rte_ethdev.c > /* add address to the hardware */ > - if (*dev->dev_ops->mac_addr_add) > + if (*dev->dev_ops->mac_addr_add && > + dev->data->mac_pool_sel[i] & (1ULL << pool)) > (*dev->dev_ops->mac_addr_add)(dev, &addr, i, pool); > + /* Update pool bitmap in NIC data structure */ > + dev->data->mac_pool_sel[index] = 0; Reset is a better word than "Update" in this case. But do we really need a comment for that? > +#define ETH_MQ_RX_RSS_FLAG 0x1 > +#define ETH_MQ_RX_DCB_FLAG 0x2 > +#define ETH_MQ_RX_VMDQ_FLAG 0x4 Need a comment to know where these flags can be used. > enum rte_eth_rx_mq_mode { > - ETH_MQ_RX_NONE = 0, /**< None of DCB,RSS or VMDQ mode */ > - > - ETH_MQ_RX_RSS, /**< For RX side, only RSS is on */ > - ETH_MQ_RX_DCB, /**< For RX side,only DCB is on. */ > - ETH_MQ_RX_DCB_RSS, /**< Both DCB and RSS enable */ > - > - ETH_MQ_RX_VMDQ_ONLY, /**< Only VMDQ, no RSS nor DCB */ > - ETH_MQ_RX_VMDQ_RSS, /**< RSS mode with VMDQ */ > - ETH_MQ_RX_VMDQ_DCB, /**< Use VMDQ+DCB to route traffic to queues */ > - ETH_MQ_RX_VMDQ_DCB_RSS, /**< Enable both VMDQ and DCB in VMDq */ > + /**< None of DCB,RSS or VMDQ mode */ > + ETH_MQ_RX_NONE = 0, > + > + /**< For RX side, only RSS is on */ > + ETH_MQ_RX_RSS = ETH_MQ_RX_RSS_FLAG, > + /**< For RX side,only DCB is on. */ > + ETH_MQ_RX_DCB = ETH_MQ_RX_DCB_FLAG, > + /**< Both DCB and RSS enable */ > + ETH_MQ_RX_DCB_RSS = ETH_MQ_RX_RSS_FLAG | ETH_MQ_RX_DCB_FLAG, > + > + /**< Only VMDQ, no RSS nor DCB */ > + ETH_MQ_RX_VMDQ_ONLY = ETH_MQ_RX_VMDQ_FLAG, > + /**< RSS mode with VMDQ */ > + ETH_MQ_RX_VMDQ_RSS = ETH_MQ_RX_RSS_FLAG | ETH_MQ_RX_VMDQ_FLAG, > + /**< Use VMDQ+DCB to route traffic to queues */ > + ETH_MQ_RX_VMDQ_DCB = ETH_MQ_RX_VMDQ_FLAG | ETH_MQ_RX_DCB_FLAG, > + /**< Enable both VMDQ and DCB in VMDq */ > + ETH_MQ_RX_VMDQ_DCB_RSS = ETH_MQ_RX_RSS_FLAG | ETH_MQ_RX_DCB_FLAG | > + ETH_MQ_RX_VMDQ_FLAG, > }; Why not simply remove all these combinations and keep only flags? Please keep it simple. > + /**< Specify the queue range belongs to VMDQ pools if VMDQ applicable */ > + uint16_t vmdq_queue_base; > + uint16_t vmdq_queue_num; If comment is before, it should be /** not /**<. > + uint16_t vmdq_pool_base; /** < Specify the start pool ID of VMDQ pools */ There is a typo with the space --^ Please, when writing comments, ask yourself if each word is required and how it can be shorter. Example here: /**< first ID of VMDQ pools */ Conclusion: NACK There are only few typos and minor things but it would help to have more careful reviews. Having a list of people at the beginning of the patch didn't help in this case. Thanks for your attention -- Thomas