From: David Marchand <david.marchand@redhat.com>
To: "Morrissey, Sean" <sean.morrissey@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>,
"Laatz, Kevin" <kevin.laatz@intel.com>,
Gaetan Rivet <gaetan.rivet@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v2] Revert "eal: fix parsing option --telemetry"
Date: Thu, 25 Jul 2019 10:42:31 +0200 [thread overview]
Message-ID: <CAJFAV8xnAXhNjFqgf9Cry+UbgLZ5aQqXJm5=BtTBcTfdiw+Pjg@mail.gmail.com> (raw)
In-Reply-To: <A21CD6D18EB13E4B84881D350AF40D092A6556AE@irsmsx105.ger.corp.intel.com>
On Thu, Jul 25, 2019 at 10:38 AM Morrissey, Sean
<sean.morrissey@intel.com> wrote:
>
> Subject: Re: [PATCH v2] Revert "eal: fix parsing option --telemetry"
>
> 24/07/2019 18:28, Morrissey, Sean:
> >
> > Subject: Re: [PATCH v2] Revert "eal: fix parsing option --telemetry"
> >
> > 24/07/2019 17:20, Sean Morrissey:
> > > This reverts commit debacba0297fbe214b4185a9791e6a9fdf6642ba.
> > >
> > > Reverting this patch as it currently breaks the initialization of
> > > telemetry, more investigation is ongoing to fix the issue for the
> > > printed error message for unrecognized argument.
> > >
> > > Signed-off-by: Sean Morrissey <sean.morrissey@intel.com>
> >
> > It's very disapointing.
> > Did you or the reviewer tested the previous patch?
> >
> > The reporter of the bug tested this and verified functionality and closed the internal bug.
>
> So the reverted commit is supposed to work?
> I won't apply this revert until I fully understand what happens.
>
> The patch that I sent up was to remove an "unrecognized option telemetry" warning message, which the patch removed and was tested to ensure the message was removed. Further testing, after the patch was sent up, revealed that the unix domain socket, which is required by telemetry consumers, was no longer being created, rendering the telemetry functionality non-functional.
> On further investigation, the full fix involves a change in the EAL command line parameter handling, which is probably too risky for RC3.
> This revert will allow telemetry to function again, but with the erroneous message still in place.
> We will aim to fix in the next release.
Might be good to look and revisit the rte_option api.
> --------------------------------------------------------------
> Intel Research and Development Ireland Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
>
>
> This e-mail and any attachments may contain confidential material for the sole
> use of the intended recipient(s). Any review or distribution by others is
> strictly prohibited. If you are not the intended recipient, please contact the
> sender and delete all copies.
>
Can you contact your IT and get this footer removed ?
Thanks.
--
David Marchand
next prev parent reply other threads:[~2019-07-25 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 15:20 Sean Morrissey
2019-07-24 15:31 ` Thomas Monjalon
2019-07-24 16:28 ` Morrissey, Sean
2019-07-24 21:34 ` Thomas Monjalon
2019-07-25 8:38 ` Morrissey, Sean
2019-07-25 8:42 ` David Marchand [this message]
2019-07-28 19:55 ` Thomas Monjalon
2019-07-29 8:40 ` David Marchand
2019-07-29 9:22 ` Gaëtan Rivet
2019-07-29 20:06 ` Thomas Monjalon
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='CAJFAV8xnAXhNjFqgf9Cry+UbgLZ5aQqXJm5=BtTBcTfdiw+Pjg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.com \
--cc=kevin.laatz@intel.com \
--cc=sean.morrissey@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).