DPDK patches and discussions
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 4/5] mlx5: add support for flow director
Date: Thu, 18 Feb 2016 17:10:16 +0100	[thread overview]
Message-ID: <20160218161016.GQ27079@6wind.com> (raw)
In-Reply-To: <20160217171343.GA11736@bricha3-MOBL3>

Hi Bruce,

On Wed, Feb 17, 2016 at 05:13:44PM +0000, Bruce Richardson wrote:
> On Fri, Jan 29, 2016 at 11:32:01AM +0100, Adrien Mazarguil wrote:
> > From: Yaacov Hazan <yaacovh@mellanox.com>
> > 
> > Add support for flow director filters (RTE_FDIR_MODE_PERFECT and
> > RTE_FDIR_MODE_PERFECT_MAC_VLAN modes).
> > 
> > This feature requires MLNX_OFED 3.2.
> > 
> > Signed-off-by: Yaacov Hazan <yaacovh@mellanox.com>
> > Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
> > ---
> Hi Adrien, Yaacov,
> 
> this patch raises a lot of warnings (17) with checkpatch. Can you perhaps look
> to see if this number can be reduced.

We actually did it before submitting that patch, there is indeed a bunch of
remaining warnings that have been left on purpose. Not sure if we have the
same configuration for checkpatch, but they should fall into the following
categories:

- "WARNING: return of an errno should typically be negative" - All return
  values are documented in the code. Since this PMD uses syscalls in its
  control path, it uses positive errno values internally for
  consistency. Public callback functions however return negative error
  values.

- "WARNING: line over 80 characters" - Well, although I'm a big fan of the
  80 characters limit, breaking those would have made the code harder to
  read.

- "WARNING: Missing a blank line after declarations" - It's actually a
  declaration through a macro, there is no missing blank line.

- "WARNING: networking block comments don't use an empty /* line" - Not sure
  if we really care? I don't particularly mind.

- "CHECK: Comparison to NULL could be written "!" - I do not mind either,
  writing the full check seems clearer to me.

- "CHECK: Unnecessary parentheses around fdir_info->mask" - Looks like a
  valid, although minor error.

Please tell me which of these still need to be fixed.

-- 
Adrien Mazarguil
6WIND

  reply	other threads:[~2016-02-18 16:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 10:31 [dpdk-dev] [PATCH 0/5] Add flow director and RX VLAN stripping support Adrien Mazarguil
2016-01-29 10:31 ` [dpdk-dev] [PATCH 1/5] mlx5: refactor special flows handling Adrien Mazarguil
2016-01-29 10:31 ` [dpdk-dev] [PATCH 2/5] mlx5: add special flows (broadcast and IPv6 multicast) Adrien Mazarguil
2016-01-29 10:32 ` [dpdk-dev] [PATCH 3/5] mlx5: make flow steering rule generator more generic Adrien Mazarguil
2016-01-29 10:32 ` [dpdk-dev] [PATCH 4/5] mlx5: add support for flow director Adrien Mazarguil
2016-02-17 17:13   ` Bruce Richardson
2016-02-18 16:10     ` Adrien Mazarguil [this message]
2016-02-23 15:13       ` Bruce Richardson
2016-02-23 17:14         ` Thomas Monjalon
2016-02-23 17:38           ` Adrien Mazarguil
2016-01-29 10:32 ` [dpdk-dev] [PATCH 5/5] mlx5: add support for RX VLAN stripping Adrien Mazarguil
2016-02-17 17:14 ` [dpdk-dev] [PATCH 0/5] Add flow director and RX VLAN stripping support Bruce Richardson
2016-02-18 16:27   ` Adrien Mazarguil
2016-02-22 18:02 ` [dpdk-dev] [PATCH v2 " Adrien Mazarguil
2016-02-22 18:02   ` [dpdk-dev] [PATCH v2 1/5] mlx5: refactor special flows handling Adrien Mazarguil
2016-02-22 18:02   ` [dpdk-dev] [PATCH v2 2/5] mlx5: add special flows (broadcast and IPv6 multicast) Adrien Mazarguil
2016-02-22 18:02   ` [dpdk-dev] [PATCH v2 3/5] mlx5: make flow steering rule generator more generic Adrien Mazarguil
2016-02-22 18:02   ` [dpdk-dev] [PATCH v2 4/5] mlx5: add support for flow director Adrien Mazarguil
2016-02-22 18:02   ` [dpdk-dev] [PATCH v2 5/5] mlx5: add support for RX VLAN stripping Adrien Mazarguil
2016-03-03 14:26   ` [dpdk-dev] [PATCH v3 0/5] Add flow director and RX VLAN stripping support Adrien Mazarguil
2016-03-03 14:26     ` [dpdk-dev] [PATCH v3 1/5] mlx5: refactor special flows handling Adrien Mazarguil
2016-03-03 14:26     ` [dpdk-dev] [PATCH v3 2/5] mlx5: add special flows (broadcast and IPv6 multicast) Adrien Mazarguil
2016-03-03 14:26     ` [dpdk-dev] [PATCH v3 3/5] mlx5: make flow steering rule generator more generic Adrien Mazarguil
2016-03-03 14:26     ` [dpdk-dev] [PATCH v3 4/5] mlx5: add support for flow director Adrien Mazarguil
2016-03-03 14:26     ` [dpdk-dev] [PATCH v3 5/5] mlx5: add support for RX VLAN stripping Adrien Mazarguil
2016-03-09 16:11     ` [dpdk-dev] [PATCH v3 0/5] Add flow director and RX VLAN stripping support 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=20160218161016.GQ27079@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=bruce.richardson@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).