From: Luca Boccassi <bluca@debian.org>
To: Remy Horton <remy.horton@intel.com>, dev@dpdk.org
Cc: wenzhuo.lu@intel.com, wei.dai@intel.com
Subject: Re: [PATCH 2/2] ethdev: pre-emptively document rte_eth_dev_reset error code
Date: Tue, 24 Oct 2017 13:01:00 +0100 [thread overview]
Message-ID: <1508846460.29685.19.camel@debian.org> (raw)
In-Reply-To: <8de2f02a-5434-3fb8-8fed-7bb013f6c49c@intel.com>
On Tue, 2017-10-24 at 07:18 +0100, Remy Horton wrote:
> On 19/10/2017 17:14, Luca Boccassi wrote:
> [..]
> > We've adapted and used these patches with the early
> > rte_eth_dev_reset
> > for a year in production now, and we had a customer who requested
> > it
> > since they were running into the problem it solves (PF flaps).
> >
> > I have adapted them on the latest 17.11 tree and tested with X540
> > 10gbit cards, and it seems to work as before. Should I send an RFC
> > and
> > CC all of you?
>
> Since it sounds stable, probably best to post the updated/rebased
> patch.
> Should get merged as long as nothing breaks.
I can send an RFC later today.
>
> > Incidentally, are there specific reasons why the VF functionality
> > was
> > dropped since the first patches were sent?
>
> I'm personally not sure, but the others should know.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2017-10-24 12:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 13:48 [PATCH 1/2] ethdev: document rte_eth_dev_reset return codes luca.boccassi
2017-10-19 13:48 ` [PATCH 2/2] ethdev: pre-emptively document rte_eth_dev_reset error code luca.boccassi
2017-10-19 14:53 ` Remy Horton
2017-10-19 16:14 ` Luca Boccassi
2017-10-24 6:18 ` Remy Horton
2017-10-24 12:01 ` Luca Boccassi [this message]
2017-10-23 22:11 ` Thomas Monjalon
2017-10-24 12:00 ` Luca Boccassi
2017-10-19 14:52 ` [PATCH 1/2] ethdev: document rte_eth_dev_reset return codes Remy Horton
2017-10-24 11:03 ` [PATCH v2 " luca.boccassi
2017-10-24 11:03 ` [PATCH v2 2/2] ethdev: pre-emptively document rte_eth_dev_reset error code luca.boccassi
2017-10-24 12:29 ` Thomas Monjalon
2017-10-24 12:27 ` [PATCH v2 1/2] ethdev: document rte_eth_dev_reset return codes Thomas Monjalon
2017-10-24 13:19 ` Luca Boccassi
2017-10-24 13:19 ` [PATCH v3 1/2] ethdev: document error codes of reset luca.boccassi
2017-10-24 13:19 ` [PATCH v3 2/2] ethdev: document new error code for reset luca.boccassi
2017-10-24 20:41 ` [PATCH v3 1/2] ethdev: document error codes of reset Ferruh Yigit
2017-10-25 12:01 ` Luca Boccassi
2017-10-25 16:08 ` 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=1508846460.29685.19.camel@debian.org \
--to=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=remy.horton@intel.com \
--cc=wei.dai@intel.com \
--cc=wenzhuo.lu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.