DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: maciej.czekaj@caviumnetworks.com, dev@dpdk.org
Cc: shahafs@mellanox.com, thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH] net/thunderx: Convert ThunderX VNIC PMD to new offload API
Date: Fri, 12 Jan 2018 18:34:05 +0000	[thread overview]
Message-ID: <5795a502-77cf-2b33-a723-bb7b43ec6d82@intel.com> (raw)
In-Reply-To: <1514985137-2653-1-git-send-email-maciej.czekaj@caviumnetworks.com>

On 1/3/2018 1:12 PM, maciej.czekaj@caviumnetworks.com wrote:
> From: Maciej Czekaj <maciej.czekaj@caviumnetworks.com>
> 
> This patch removes all references to old-style offload API
> replacing them with new offload flags.
> 
> Signed-off-by: Maciej Czekaj <maciej.czekaj@caviumnetworks.com>

<...>

>  
>  	dev_info->default_txconf = (struct rte_eth_txconf) {
>  		.tx_free_thresh = NICVF_DEFAULT_TX_FREE_THRESH,
> -		.txq_flags =
> -			ETH_TXQ_FLAGS_NOMULTSEGS  |
> -			ETH_TXQ_FLAGS_NOREFCOUNT  |
> -			ETH_TXQ_FLAGS_NOMULTMEMP  |
> -			ETH_TXQ_FLAGS_NOVLANOFFL  |
> -			ETH_TXQ_FLAGS_NOXSUMSCTP,
> +		.txq_flags = ETH_TXQ_FLAGS_IGNORE,

I am not sure about this, Shahafs may comment better, shouldn't application
decide to set "ETH_TXQ_FLAGS_IGNORE" or not, instead of having this in default
configuration?

<...>

> +	if ((conf_tx_offloads & tx_offload_capa) != conf_tx_offloads) {
> +		PMD_INIT_LOG(ERR, "Some Tx offloads are not supported "
> +		      "requested 0x%lx supported 0x%lx\n",
> +		      conf_tx_offloads, tx_offload_capa);

This is broken for 32bits, using PRIx64 instead of "lx" makes your code more
portable.

  reply	other threads:[~2018-01-12 18:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 13:12 maciej.czekaj
2018-01-12 18:34 ` Ferruh Yigit [this message]
2018-01-15 14:49   ` Maciej Czekaj
2018-01-15 17:45     ` Ferruh Yigit
2018-01-16  9:32       ` Maciej Czekaj
2018-01-16 10:10         ` Ferruh Yigit
2018-01-16 13:50   ` Shahaf Shuler
2018-01-18 13:06 ` [dpdk-dev] [PATCH v2] " maciej.czekaj
2018-01-18 16:41   ` Ferruh Yigit

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=5795a502-77cf-2b33-a723-bb7b43ec6d82@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=maciej.czekaj@caviumnetworks.com \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    /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).