DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xing, Beilei" <beilei.xing@intel.com>
To: Martin Weiser <martin.weiser@allegro-packets.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Subject: Re: [dpdk-dev] DEV_RX_OFFLOAD_SCATTER not available in i40e an cxgbe
Date: Fri, 21 Sep 2018 07:38:44 +0000	[thread overview]
Message-ID: <94479800C636CB44BD422CB454846E013222CCFC@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <cd459dc3-8b5b-94e7-8d59-7f7ffe0fdd6b@allegro-packets.com>

Hi Martin,

Thanks for the catch, patch has been sent.

BR,
Beilei

> -----Original Message-----
> From: Martin Weiser [mailto:martin.weiser@allegro-packets.com]
> Sent: Tuesday, September 18, 2018 5:24 PM
> To: dev@dpdk.org
> Cc: Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>;
> Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
> Subject: DEV_RX_OFFLOAD_SCATTER not available in i40e an cxgbe
> 
> Hi,
> 
> is there a specific reason that the rx offload capability
> DEV_RX_OFFLOAD_SCATTER is not available in the i40e and cxgbe drivers in
> DPDK 18.08?
> We previously used this feature with DPDK 17.11 to handle jumbo frames
> while using 2k mbufs and it worked without a problem.
> It also seems that simply adding the flag to dev_info->rx_offload_capa makes
> it work again.
> 
> Best regards,
> Martin


      parent reply	other threads:[~2018-09-21  7:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18  9:24 Martin Weiser
2018-09-19 15:23 ` Rahul Lakkireddy
2018-09-21  7:38 ` Xing, Beilei [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=94479800C636CB44BD422CB454846E013222CCFC@SHSMSX101.ccr.corp.intel.com \
    --to=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=martin.weiser@allegro-packets.com \
    --cc=qi.z.zhang@intel.com \
    --cc=rahul.lakkireddy@chelsio.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).