DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: <dev@dpdk.org>, Declan Doherty <declan.doherty@intel.com>,
	Chas Williams <chas3@att.com>
Subject: Re: [dpdk-dev] [PATCH v1 0/3] ethdev: document more retained across restart
Date: Wed, 9 Jan 2019 10:15:47 +0300	[thread overview]
Message-ID: <d98613c9-4544-e398-8cf2-b18a2228811d@solarflare.com> (raw)
In-Reply-To: <10d9a6ab-d2b3-69a8-9155-2c8a50079564@intel.com>

On 1/8/19 5:52 PM, Ferruh Yigit wrote:
> On 12/19/2018 6:22 AM, Andrew Rybchenko wrote:
>> The patch series tries to improve documentation of what is retained
>> across default restart.
> Overall makes sense to add below items into retained list, only concern if is
> there any PMD conflicts with these information, they should either updated with
> this patch or at least notified about expectation change.

 From my point of view it is just clarification of the required behaviour.
MTU is required because of flag which may be used to advertise that
it is impossible to change in started state (otherwise the behaviour for
different PMDs will be absolutely different).
Default MAC is just cosmetics because of MAC address list is already
mentioned and the only goal is to highlight since these are different
features from the feature list point of view.
All-multicast is a part of Rx mode.

In fact I recall that net/bonding does not preserve all-multicast
(CC maintainers). If there is an agreement to fix it, I can take
a look - it should not be hard to fix.

In general I think that notification is sufficient in this case.

>> Andrew Rybchenko (3):
>>    ethdev: advertise MTU as retained across device stop/start
>>    ethdev: advertise default MAC as retained on device restart
>>    ethdev: highlight that all-multicast is retained on restart
>>
>>   lib/librte_ethdev/rte_ethdev.h | 6 ++++--
>>   1 file changed, 4 insertions(+), 2 deletions(-)
>>

  reply	other threads:[~2019-01-09  7:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10  7:51 [dpdk-dev] [RFC PATCH " Andrew Rybchenko
2018-10-10  7:51 ` [dpdk-dev] [RFC PATCH 1/3] ethdev: advertise MTU as retained across device stop/start Andrew Rybchenko
2018-10-10  7:51 ` [dpdk-dev] [RFC PATCH 2/3] ethdev: advertise default MAC as retained on device restart Andrew Rybchenko
2018-10-10  8:53   ` Thomas Monjalon
2018-10-10  9:05     ` Andrew Rybchenko
2018-10-10  9:35       ` Thomas Monjalon
2018-10-10  7:51 ` [dpdk-dev] [RFC PATCH 3/3] ethdev: highlight that all-multicast is retained on restart Andrew Rybchenko
2018-12-19  6:22 ` [dpdk-dev] [PATCH v1 0/3] ethdev: document more retained across restart Andrew Rybchenko
2018-12-19  6:22   ` [dpdk-dev] [PATCH v1 1/3] ethdev: advertise MTU as retained across device stop/start Andrew Rybchenko
2018-12-19  6:22   ` [dpdk-dev] [PATCH v1 2/3] ethdev: advertise default MAC as retained on device restart Andrew Rybchenko
2018-12-19  6:23   ` [dpdk-dev] [PATCH v1 3/3] ethdev: highlight that all-multicast is retained on restart Andrew Rybchenko
2019-01-08 14:52   ` [dpdk-dev] [PATCH v1 0/3] ethdev: document more retained across restart Ferruh Yigit
2019-01-09  7:15     ` Andrew Rybchenko [this message]
2019-01-10  2:03       ` WILLIAMS, CHARLES J
2019-01-23 12:23         ` Andrew Rybchenko
2019-03-19 13:21   ` Yigit, Ferruh
2019-03-19 13:21     ` Yigit, Ferruh
2019-03-20 14:26     ` Thomas Monjalon
2019-03-20 14:26       ` Thomas Monjalon
2019-03-20 15:25       ` Ferruh Yigit
2019-03-20 15:25         ` Ferruh Yigit
2019-03-20 15:32         ` Thomas Monjalon
2019-03-20 15:32           ` Thomas Monjalon
2019-03-20 16:53           ` Ferruh Yigit
2019-03-20 16:53             ` 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=d98613c9-4544-e398-8cf2-b18a2228811d@solarflare.com \
    --to=arybchenko@solarflare.com \
    --cc=chas3@att.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \
    /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).