All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Moti Haimovsky <motih@mellanox.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v4] net/mlx4: enhance Rx packet type offloads
Date: Tue, 7 Nov 2017 09:43:27 +0100	[thread overview]
Message-ID: <20171107084327.GC24849@6wind.com> (raw)
In-Reply-To: <1509902816-26299-1-git-send-email-motih@mellanox.com>

On Sun, Nov 05, 2017 at 07:26:56PM +0200, Moti Haimovsky wrote:
> This patch enhances the Rx packet type offload to also report the L4
> protocol information in the hw ptype filled by the PMD for each received
> packet.
> 
> Signed-off-by: Moti Haimovsky <motih@mellanox.com>

Patch looks fine therefore:

Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

Although in the end you didn't initialize mlx4_ptype_table[] using a loop
(went all the way back to static array initialization) and I'm still
wondering why since you never replied on that topic.

Another comment: please remember to send patch updates as replies to their
previous iteration. If you search for "enhance Rx packet type offloads"
in [1], you notice they're not part of the same thread. While minor this
doesn't help the review process.

Regarding your previous reply about mlx4_dev_supported_ptypes_get():

[...]
> > > +
> > > +   if (dev->rx_pkt_burst == mlx4_rx_burst)
> > > +           return ptypes;
> > > +   return NULL;
> >
> > How about just returning the array regardless?
>
> From DPDK documentation (and as done in other drivers):
> http://dpdk.org/doc/api/rte__ethdev_8h.html#aa63202d322632467f9cc5fc460e04ea4
> Note
> Better to invoke this API after the device is already started or rx burst
> function is decided, to obtain correct supported ptypes.
> if a given PMD does not report what ptypes it supports, then the supported
> ptype count is reported as 0.
> 
> In our case rx_pkt_burst can also point to mlx4_rx_burst_removed

Right, and it doesn't hurt. My point was that mlx4_rx_burst_removed() is set
as a safety when closing/stopping the device, no more Rx in that case. The
mlx4 PMD currently exposes a single Rx function which does support
everything, not multiple optimized ones with fewer capabilities, which is
the actual reason behind checking the current Rx function.

[1] http://dpdk.org/ml/archives/dev/2017-November/

-- 
Adrien Mazarguil
6WIND

  reply	other threads:[~2017-11-07  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-05 17:26 [PATCH v4] net/mlx4: enhance Rx packet type offloads Moti Haimovsky
2017-11-07  8:43 ` Adrien Mazarguil [this message]
2017-11-07 11:47   ` 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=20171107084327.GC24849@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=motih@mellanox.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 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.