DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Moti Haimovsky <motih@mellanox.com>
Cc: wenzhuo.lu@intel.com, dev@dpdk.org, techboard@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v6] app/testpmd: no Rx or Tx offloads by default
Date: Wed, 31 Jan 2018 18:19:25 +0100	[thread overview]
Message-ID: <2371406.ix6cSJql9R@xps> (raw)
In-Reply-To: <1517417958-30594-1-git-send-email-motih@mellanox.com>

31/01/2018 17:59, Moti Haimovsky:
> Removed the hardcoded preconfigured Rx and Tx offload configuration
> from testpmd and changed the Rx offload command line parameters from
> disable to enable.

The description must be updated because v6 does not remove the last
default Tx offload.

> Testers who wish to use these offloads will now have to explicitly
> write them in the command-line when running testpmd.
> The above does not apply to Rx crc-strip and Tx MBUF_FAST_FREE which
> were not removed and are silently dropped in ports that do not
> support them.

Can be added here: It has been decided by the Technical Board.

> Motivation:
> Some PMDs such at the mlx4 may not implement all the offloads.
> After the offload API rework assuming no offload is enabled by default,
>   commit ce17eddefc20 ("ethdev: introduce Rx queue offloads API")
>   commit cba7f53b717d ("ethdev: introduce Tx queue offloads API") trying
> to enable a not supported offload is clearly an error which will cause
> configuration failing.
> 
> Considering that testpmd is an application to test the PMD, it should
> not fail on a configuration which was not explicitly requested.
> The behavior of this test application is then turned to an opt-in
> model.
> 
> Signed-off-by: Moti Haimovsky <motih@mellanox.com>
> ---
> V6:
> Returned DEV_RX_OFFLOAD_CRC_STRIP and DEV_TX_OFFLOAD_MBUF_FAST_FREE
> as default config values.

Thank you, it reflects what has been decided today in the
Technical Board meeting.
We discussed the need of not having offloads by default in testpmd.
There are only two exceptions for 18.02:
	- Rx CRC strip is often required, and the flag could be completely removed
or reversed in 18.05.
	- Tx fast free could be discussed more.

  reply	other threads:[~2018-01-31 17:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23  8:11 [dpdk-dev] [PATCH] app/testpmd: do not enable Rx " Moti Haimovsky
2018-01-25  1:11 ` Lu, Wenzhuo
2018-01-25  9:04   ` Thomas Monjalon
2018-01-25 16:01     ` Stephen Hemminger
2018-01-26  7:31       ` Lu, Wenzhuo
2018-01-26  7:49         ` Thomas Monjalon
2018-01-26  7:30     ` Lu, Wenzhuo
2018-01-26  7:48       ` Thomas Monjalon
2018-01-26  8:06         ` Lu, Wenzhuo
2018-01-26  8:35           ` Thomas Monjalon
2018-01-27 18:14             ` Shahaf Shuler
2018-01-29 11:33 ` [dpdk-dev] [PATCH v2] " Moti Haimovsky
2018-01-29 11:52   ` Thomas Monjalon
2018-01-30  8:44   ` [dpdk-dev] [PATCH v3] " Moti Haimovsky
2018-01-30  9:00     ` [dpdk-dev] [PATCH v4] " Moti Haimovsky
2018-01-31  3:16       ` Lu, Wenzhuo
2018-01-31 11:55       ` [dpdk-dev] [PATCH v5] " Moti Haimovsky
2018-01-31 16:59         ` [dpdk-dev] [PATCH v6] app/testpmd: no Rx or Tx " Moti Haimovsky
2018-01-31 17:19           ` Thomas Monjalon [this message]
2018-01-31 17:32           ` [dpdk-dev] [PATCH v7] app/testpmd: removed preconf Rx VLAN offloads Moti Haimovsky
2018-01-31 21:09             ` 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=2371406.ix6cSJql9R@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=motih@mellanox.com \
    --cc=techboard@dpdk.org \
    --cc=wenzhuo.lu@intel.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 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).