DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Walukiewicz, Miroslaw" <Miroslaw.Walukiewicz@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ixgbe: fix a problem with NIC TSO offload
Date: Tue, 9 Dec 2014 18:40:50 +0000	[thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258213BE72A@IRSMSX105.ger.corp.intel.com> (raw)
In-Reply-To: <20141209171447.9954.48212.stgit@gklab-18-011.igk.intel.com>

> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of miroslaw.walukiewicz@intel.com
> Sent: Tuesday, December 09, 2014 5:15 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] ixgbe: fix a problem with NIC TSO offload
> 
> From: Miroslaw Walukiewicz <miroslaw.walukiewicz@intel.com>
> 
> The patch fixes a minor issue with setting up of TSO feature for
> ixgbe NICs.
> 
> The values for l4_len and tso_segsz was chagned first by txoffload mask
> and next set up in the NIC descriptor.
> 
> Signed-off-by: Mirek Walukiewicz <miroslaw.walukiewicz@intel.com>
> ---
>  lib/librte_pmd_ixgbe/ixgbe_rxtx.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/librte_pmd_ixgbe/ixgbe_rxtx.c b/lib/librte_pmd_ixgbe/ixgbe_rxtx.c
> index 8559ef6..c9c3104 100644
> --- a/lib/librte_pmd_ixgbe/ixgbe_rxtx.c
> +++ b/lib/librte_pmd_ixgbe/ixgbe_rxtx.c
> @@ -390,13 +390,13 @@ ixgbe_set_xmit_ctx(struct igb_tx_queue* txq,
>  		type_tucmd_mlhl = IXGBE_ADVTXD_TUCMD_IPV4 |
>  			IXGBE_ADVTXD_TUCMD_L4T_TCP |
>  			IXGBE_ADVTXD_DTYP_CTXT | IXGBE_ADVTXD_DCMD_DEXT;
> +		mss_l4len_idx |= tx_offload.tso_segsz << IXGBE_ADVTXD_MSS_SHIFT;
> +		mss_l4len_idx |= tx_offload.l4_len << IXGBE_ADVTXD_L4LEN_SHIFT;

Didn't  understand your comment above...
By whom tx_offload.l4_len will be changed?
As I can see, below only tx_offload_mask is updated, tx_offload is intact.
Konstantin

> 
>  		tx_offload_mask.l2_len = ~0;
>  		tx_offload_mask.l3_len = ~0;
>  		tx_offload_mask.l4_len = ~0;
>  		tx_offload_mask.tso_segsz = ~0;
> -		mss_l4len_idx |= tx_offload.tso_segsz << IXGBE_ADVTXD_MSS_SHIFT;
> -		mss_l4len_idx |= tx_offload.l4_len << IXGBE_ADVTXD_L4LEN_SHIFT;
>  	} else { /* no TSO, check if hardware checksum is needed */
>  		if (ol_flags & PKT_TX_IP_CKSUM) {
>  			type_tucmd_mlhl = IXGBE_ADVTXD_TUCMD_IPV4;


  reply	other threads:[~2014-12-09 19:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09 17:14 miroslaw.walukiewicz
2014-12-09 18:40 ` Ananyev, Konstantin [this message]
2014-12-09 18:44   ` Walukiewicz, Miroslaw

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=2601191342CEEE43887BDE71AB977258213BE72A@IRSMSX105.ger.corp.intel.com \
    --to=konstantin.ananyev@intel.com \
    --cc=Miroslaw.Walukiewicz@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).