DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev-bounces@dpdk.org, dev@dpdk.org
Cc: nd@arm.com
Subject: Re: [dpdk-dev] [PATCH] test/virtual_pmd: Add DEV_RX_OFFLOAD_CRC_STRIP to virtual driver
Date: Wed, 4 Jul 2018 10:45:00 +0100	[thread overview]
Message-ID: <682b1c7a-6ab8-fc25-e8b4-30650f842b99@intel.com> (raw)
In-Reply-To: <6a272915-d628-e984-408c-2c89b3c0fdeb@intel.com>

On 7/4/2018 10:34 AM, Ferruh Yigit wrote:
> On 7/4/2018 2:31 AM, dev-bounces@dpdk.org wrote:
>> Add DEV_RX_OFFLOAD_CRC_STRIP to virtual drivers since they don't
>> use CRC at all, when an application requires this offload virtual
>> PMDs should not return error.
> 
> Agreed.
> 
> Can you please check following patch [1] that has been applied to next-net which
> adds DEV_RX_OFFLOAD_CRC_STRIP to virtual devices. Is this solves your issue?

My bad, oversight your patch. You already aware of the patch mentioned and this
is to fix a missing part there. Patch looks good, thanks.


> 
> [1]
> https://patches.dpdk.org/patch/41957/
> 
>>
>> Fixes: b219c8c("test: enable HW CRC strip by default")
>>
>> Signed-off-by: Phil Yang <phil.yang@arm.com>

Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

>> ---
>>  test/test/virtual_pmd.c | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/test/test/virtual_pmd.c b/test/test/virtual_pmd.c
>> index f8ddc2d..591b309 100644
>> --- a/test/test/virtual_pmd.c
>> +++ b/test/test/virtual_pmd.c
>> @@ -91,6 +91,7 @@ virtual_ethdev_info_get(struct rte_eth_dev *dev __rte_unused,
>>  	dev_info->max_tx_queues = (uint16_t)512;
>>  
>>  	dev_info->min_rx_bufsize = 0;
>> +	dev_info->rx_offload_capa = DEV_RX_OFFLOAD_CRC_STRIP;
>>  }
>>  
>>  static int
>>
> 

  reply	other threads:[~2018-07-04  9:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04  1:31 Phil Yang
2018-07-04  9:34 ` Ferruh Yigit
2018-07-04  9:45   ` Ferruh Yigit [this message]
2018-07-04 18:35     ` 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=682b1c7a-6ab8-fc25-e8b4-30650f842b99@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev-bounces@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=nd@arm.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).