From: "Walsh, Conor" <conor.walsh@intel.com>
To: "Power, Ciara" <ciara.power@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] usertools/telemetry: add listing of available file prefixes
Date: Fri, 8 Oct 2021 08:20:46 +0000 [thread overview]
Message-ID: <PH0PR11MB52079713B8ED6378C57032F6FFB29@PH0PR11MB5207.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MN2PR11MB38215A9E4B60BC0DFE480020E6B19@MN2PR11MB3821.namprd11.prod.outlook.com>
<snip>
>
> >+
> >+def list_fp():
> >+ """ List all available file-prefixes to user """
> >+ print("Valid file-prefixes:\n")
>
> Nit: I think it might be cleaner to move this down to just before the file
> prefixes print out, so it doesn't print out when no apps are available.
>
> >+ path = get_dpdk_runtime_dir('')
> >+
> >+ sockets = glob.glob(os.path.join(path, "*", SOCKET_NAME + "*"))
> >+ prefixes = []
> >+ if not sockets:
> >+ print("\tNo DPDK apps with telemetry enabled available")
> >+ for s in sockets:
> >+ prefixes.append(os.path.relpath(os.path.dirname(s), start=path))
> >+ for p in sorted(set(prefixes)):
> >+ print(p)
> >+ print_socket_options(p, glob.glob(os.path.join(path, p,
> >+ SOCKET_NAME +
> >+ "*")))
> <snip>
>
> Asides from that one small comment,
>
> Acked-by: Ciara Power <ciara.power@intel.com>
>
> Thanks!
Hi Ciara,
Thanks for the ack, I will address your comment in v2.
/Conor.
next prev parent reply other threads:[~2021-10-08 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 15:00 Conor Walsh
2021-10-07 15:47 ` Power, Ciara
2021-10-08 8:20 ` Walsh, Conor [this message]
2021-10-11 9:49 ` [dpdk-dev] [PATCH v2] usertools/telemetry: add list of available file-prefixes Conor Walsh
2021-10-11 9:53 ` Walsh, Conor
2021-10-13 13:01 ` Walsh, Conor
2021-10-14 19:08 ` David Marchand
2021-10-18 10:09 ` [dpdk-dev] [PATCH v3] " Conor Walsh
2021-10-19 13:34 ` David Marchand
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=PH0PR11MB52079713B8ED6378C57032F6FFB29@PH0PR11MB5207.namprd11.prod.outlook.com \
--to=conor.walsh@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
/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).