From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] usertools: reduce devbind status output
Date: Wed, 26 Apr 2017 15:09:04 +0200 [thread overview]
Message-ID: <2699850.F1Pslrmx9H@xps> (raw)
In-Reply-To: <20170426115810.495-1-ferruh.yigit@intel.com>
26/04/2017 13:58, Ferruh Yigit:
> Script displays status for all device types and output is much
> longer than it used to be. This makes harder to read script output.
>
> This patch reduces output to the script into a device group which can be
> defined with new -t,--type parameter to script.
>
> Supported types:
> net
> crypto
> mempool
> eventdev
>
> If no device type provided status will print net devices by default.
>
> Sample usage:
> ./usertools/dpdk-devbind.py -s -t mempool
[...]
> + -t, --type:
> + Select device group to print status.
> + Device group can be network, crypto, eventdev or mempool.
> + Type argument can be emitted, by default "network" group used.
s/emitted/omitted/
I think it would be better to default to all types.
next prev parent reply other threads:[~2017-04-26 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 11:58 [PATCH] usertools: reduce devbind status output Ferruh Yigit
2017-04-26 13:09 ` Thomas Monjalon [this message]
2017-04-27 17:55 ` [PATCH v2] usertools: add status-dev argument to devbind Ferruh Yigit
2017-04-30 12:45 ` 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=2699850.F1Pslrmx9H@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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.