DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Alejandro Lucero <alejandro.lucero@netronome.com>,
	Maciej Czekaj <maciej.czekaj@caviumnetworks.com>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Xiao Wang <xiao.w.wang@intel.com>,
	Santosh Shukla <santosh.shukla@caviumnetworks.com>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	Shijith Thotton <shijith.thotton@cavium.com>,
	Srisivasubramanian Srinivasan <ssrinivasan@cavium.com>
Cc: Andrew Rybchenko <arybchenko@solarflare.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Shreyansh Jain <shreyansh.jain@nxp.com>, dpdk-dev <dev@dpdk.org>,
	Beilei Xing <beilei.xing@intel.com>,
	Tetsuya Mukawa <mtetsuyah@gmail.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [dpdk-dev] Remaining old offloading API usage in PMDs
Date: Tue, 22 May 2018 15:12:16 +0100	[thread overview]
Message-ID: <37887500-61db-f2d6-d647-0de83cb3860a@intel.com> (raw)
In-Reply-To: <9a1b4500-d354-bdef-45d3-7d6eeacfb54b@intel.com>

On 5/11/2018 11:45 AM, Ferruh Yigit wrote:
> Some PMDs are still using old offloading API related variables, thanks to Andrew
> for reporting it.
> 
> Maintainers of related PMDs are cc'ed.
> Please check following list and provide a fix ASAP for it, thanks.
> 
> 
> # git grep header_split drivers/
> drivers/net/i40e/i40e_rxtx_vec_common.h:        if (rxmode->header_split == 1)
> 
> # git grep hw_vlan_filter drivers/
> drivers/net/i40e/i40e_vf_representor.c:         if
> (ethdev->data->dev_conf.rxmode.hw_vlan_filter)
> drivers/net/vhost/rte_eth_vhost.c:      if (rxmode->hw_vlan_filter)
> 
> # git grep hw_vlan_strip drivers/
> drivers/net/dpaa2/dpaa2_rxtx.c:         if
> (dev->data->dev_conf.rxmode.hw_vlan_strip)
> drivers/net/i40e/i40e_vf_representor.c:         if
> (ethdev->data->dev_conf.rxmode.hw_vlan_strip)T
> drivers/net/vhost/rte_eth_vhost.c:      internal->vlan_strip =
> rxmode->hw_vlan_strip;
> 
> # git grep hw_vlan_extend drivers/
> drivers/net/i40e/i40e_rxtx_vec_common.h:        if (rxmode->hw_vlan_extend == 1)
> 
> # git grep hw_strip_crc drivers/
> drivers/net/nfp/nfp_net.c:      rxq->crc_len = (uint8_t)
> ((dev->data->dev_conf.rxmode.hw_strip_crc) ? 0
> drivers/net/sfc/sfc_rx.c:               rxmode->hw_strip_crc = 1;
> 


Code (almost [1]) cleaned up from old API usage, thanks everybody.

But driver documentation still has some pointers from old API usage, Andrew also
reported some.

Related maintainers are cc'ed, can you please check and fix following usages:

doc/guides/prog_guide/poll_mode_drv.rst
331:For an application to use the Tx offloads API it should set the
``ETH_TXQ_FLAGS_IGNORE`` flag in the ``txq_flags`` field located in
``rte_eth_txconf`` struct.
332:In such cases it is not required to set other flags in ``txq_flags``.

doc/guides/nics/virtio.rst
237:*   ``txq_flags`` is set to ``VIRTIO_SIMPLE_FLAGS`` (0xF01), which implies:

doc/guides/nics/ixgbe.rst
105:TX vPMD only works when txq_flags is set to IXGBE_SIMPLE_FLAGS.
110:*   ETH_TXQ_FLAGS_NOMULTSEGS
112:*   ETH_TXQ_FLAGS_NOVLANOFFL
114:*   ETH_TXQ_FLAGS_NOXSUMSCTP
116:*   ETH_TXQ_FLAGS_NOXSUMUDP
118:*   ETH_TXQ_FLAGS_NOXSUMTCP

doc/guides/nics/fm10k.rst
109:TX vPMD only works when ``txq_flags`` is set to ``FM10K_SIMPLE_TX_FLAG``.
113:*   ``ETH_TXQ_FLAGS_NOMULTSEGS``
115:*   ``ETH_TXQ_FLAGS_NOVLANOFFL``
117:*   ``ETH_TXQ_FLAGS_NOXSUMSCTP``
119:*   ``ETH_TXQ_FLAGS_NOXSUMUDP``
121:*   ``ETH_TXQ_FLAGS_NOXSUMTCP``



doc/guides/nics/thunderx.rst
323:``rxmode.hw_strip_crc`` member is set to 0 in ``struct rte_eth_conf``.
329:is fixed and cannot be changed. So, even when the ``rxmode.max_rx_pkt_len``

doc/guides/nics/ixgbe.rst
71:To guarantee the constraint, configuration flags in dev_conf.rxmode will be
checked:
133:In the configuration, ensure that port_conf.rxmode.hw_ip_checksum=0.
139:As in the case of l3fwd, set configure port_conf.rxmode.hw_ip_checksum=0 to
enable vPMD.

doc/guides/nics/fm10k.rst
82:To guarantee the constraint, the following configuration flags in
``dev_conf.rxmode``
153:``rxmode.hw_strip_crc`` member is set to 0 in ``struct rte_eth_conf``.
160:is fixed and cannot be changed. So, even when the ``rxmode.max_rx_pkt_len``

doc/guides/nics/octeontx.rst
169:``rxmode.hw_strip_crc`` member is set to 0 in ``struct rte_eth_conf``.
175:is fixed and cannot be changed. So, even when the ``rxmode.max_rx_pkt_len``

doc/guides/nics/liquidio.rst
205:interface. So, CRC will be stripped even when the ``rxmode.hw_strip_crc``


[1]
Waiting nfp.

      parent reply	other threads:[~2018-05-22 14:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 10:45 Ferruh Yigit
2018-05-14 11:01 ` Shreyansh Jain
2018-05-21 12:38 ` Ferruh Yigit
2018-05-21 14:16   ` Alejandro Lucero
2018-05-21 14:33     ` Ferruh Yigit
2018-05-22 14:12 ` Ferruh Yigit [this message]

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=37887500-61db-f2d6-d647-0de83cb3860a@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=alejandro.lucero@netronome.com \
    --cc=arybchenko@solarflare.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=maciej.czekaj@caviumnetworks.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mtetsuyah@gmail.com \
    --cc=qi.z.zhang@intel.com \
    --cc=santosh.shukla@caviumnetworks.com \
    --cc=shijith.thotton@cavium.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=ssrinivasan@cavium.com \
    --cc=thomas@monjalon.net \
    --cc=wenzhuo.lu@intel.com \
    --cc=xiao.w.wang@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).