DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
	Dumitru Ceara <dceara@redhat.com>
Cc: dev@dpdk.org, konstantin.ananyev@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] net/ring: advertise multi segment TX and scatter RX.
Date: Wed, 30 Sep 2020 18:04:58 +0100	[thread overview]
Message-ID: <16b77079-5503-9e45-7ca9-85307090ca99@intel.com> (raw)
In-Reply-To: <20200929083748.GA960@bricha3-MOBL.ger.corp.intel.com>

On 9/29/2020 9:37 AM, Bruce Richardson wrote:
> On Mon, Sep 28, 2020 at 08:47:29PM +0200, Dumitru Ceara wrote:
>> Even though ring interfaces don't support any other TX/RX offloads they
>> do support sending multi segment packets and this should be advertised
>> in order to not break applications that use ring interfaces.
>>
>> Also advertise scatter RX support.
>>
>> Signed-off-by: Dumitru Ceara <dceara@redhat.com>
> 
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> 

Applied to dpdk-next-net/main, thanks.

Note:
I have added ring.ini in another patch, after it is accepted 'Scattered Rx' also 
needs to be as documented there after this patch.

      reply	other threads:[~2020-09-30 17:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 10:36 [dpdk-dev] [PATCH] net/ring: advertise multi segment support Dumitru Ceara
2020-09-22 14:21 ` Ferruh Yigit
2020-09-28  7:31   ` Dumitru Ceara
2020-09-28 10:25     ` Ferruh Yigit
2020-09-28 11:00       ` Ananyev, Konstantin
2020-09-28 12:42         ` Ferruh Yigit
2020-09-28 13:10           ` Ananyev, Konstantin
2020-09-28 13:26             ` Ferruh Yigit
2020-09-28 13:58               ` Dumitru Ceara
2020-09-28 15:02                 ` Ferruh Yigit
2020-09-28 11:01       ` Bruce Richardson
2020-09-28 12:45         ` Ferruh Yigit
2020-09-28 18:47 ` [dpdk-dev] [PATCH v2] net/ring: advertise multi segment TX and scatter RX Dumitru Ceara
2020-09-29  8:37   ` Bruce Richardson
2020-09-30 17:04     ` 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=16b77079-5503-9e45-7ca9-85307090ca99@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dceara@redhat.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@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).