DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"Xiaolong Ye" <xiaolong.ye@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v12 0/7] ethdev: add new Rx offload flags
Date: Thu, 24 Oct 2019 10:34:07 +0000	[thread overview]
Message-ID: <CY4PR1801MB1863EC73C4C76628654E78D2DE6A0@CY4PR1801MB1863.namprd18.prod.outlook.com> (raw)

<snip>
>>> So all the PMD which we aren’t currently modifying need to be have
>a log message.
>>
>> No.
>
>If you mean all PMD that is announcing the capability, yes, as you said. I
>thought you are referring to other PMDs too.
>

I was referring to the PMDs currently announcing the capability.
I will send the v13.

>> If a PMD not announced this capability, it doesn't need to check this
>flag. From
>> the PMDs that announce this capability, the ones that doesn't support
>disabling
>> the offload should log this and update the PMD config to represent
>the actual
>> status.
>>
>>>


             reply	other threads:[~2019-10-24 10:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 10:34 Pavan Nikhilesh Bhagavatula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-10-22 15:20 Pavan Nikhilesh Bhagavatula
2019-10-24  9:47 ` Ferruh Yigit
2019-10-24 10:24   ` Ferruh Yigit
2019-10-21 15:19 Pavan Nikhilesh Bhagavatula
2019-10-21 15:34 ` Ferruh Yigit
2019-10-22 10:16   ` Andrew Rybchenko
2019-10-22 14:20     ` Ferruh Yigit
2019-10-10 10:51 [dpdk-dev] [PATCH v11 " pbhagavatula
2019-10-17 12:02 ` [dpdk-dev] [PATCH v12 " pbhagavatula
2019-10-17 17:43   ` Ferruh Yigit
2019-10-18  7:32     ` Andrew Rybchenko
2019-10-18  9:42       ` Ferruh Yigit
2019-10-18 10:31         ` Andrew Rybchenko
2019-10-21 15:06           ` 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=CY4PR1801MB1863EC73C4C76628654E78D2DE6A0@CY4PR1801MB1863.namprd18.prod.outlook.com \
    --to=pbhagavatula@marvell.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=arybchenko@solarflare.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinj@marvell.com \
    --cc=thomas@monjalon.net \
    --cc=xiaolong.ye@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).