DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@mellanox.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Radu Nicolau <radu.nicolau@intel.com>,
	Declan Doherty <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/bonding: switch to new offloading flags
Date: Wed, 28 Mar 2018 19:31:50 +0000	[thread overview]
Message-ID: <AM4PR0501MB265715829138EF260A9DFEE7D2A30@AM4PR0501MB2657.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <c4f38a54-1de6-cd7a-bf99-4f8a7affa067@intel.com>

Hi Declan, Radu

Please try to answer for the below questions.

From: Ferruh Yigit, Sent: Thursday, March 22, 2018 8:14 PM
> On 3/14/2018 12:50 PM, Matan Azrad wrote:
> > Questions:
> > Have you an idea why bonding PMD doesn't adjust the slaves port
> configurations to the bonding port configuration like it does for slave queue
> configuration?
> > Is the responsibility to fill the slave port configuration structure for the
> application?
> >
> > What do you think about next configuration checks (both per port and per
> queue)?
> > 	Validate the actual bonding offloads with the bonding capability.
> > 	Validate that the queue offloads includes all the port configured
> offloads.
> 
> I don't have answers for these, perhaps Declan or Radu can help.

  reply	other threads:[~2018-03-28 19:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13 12:24 Ferruh Yigit
2018-03-14 10:40 ` Radu Nicolau
2018-03-14 12:50 ` Matan Azrad
2018-03-20 15:18   ` Ferruh Yigit
2018-03-22 18:14   ` Ferruh Yigit
2018-03-28 19:31     ` Matan Azrad [this message]
2018-03-22 18:13 ` [dpdk-dev] [PATCH v2] net/bonding: switch to new offloading API Ferruh Yigit
2018-04-06  9:57   ` Radu Nicolau
2018-04-06 10:18     ` 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=AM4PR0501MB265715829138EF260A9DFEE7D2A30@AM4PR0501MB2657.eurprd05.prod.outlook.com \
    --to=matan@mellanox.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=radu.nicolau@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).