From: Bruce Richardson <bruce.richardson@intel.com>
To: Muhammad Ahmad <muhammad.ahmad@emumba.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC] A REST API based daemon of dpdk-devbind.py
Date: Wed, 4 Mar 2020 13:59:19 +0000 [thread overview]
Message-ID: <20200304135919.GB285@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAC9Mqu99NgK38gYDQejXhdBvNJWDtihWxELS8whKvYFzSBGC1A@mail.gmail.com>
On Wed, Mar 04, 2020 at 12:11:05PM +0500, Muhammad Ahmad wrote:
> Hi,
> I have observed that the dpdk-devbind.py is an interactive tool and
> not quite useful for automated testing in CI/CD. We are planning to
> create “dpdk-usertools-server” for making it streamlined.
> The idea is to create a separate application, which provides REST interface to:
> - Query the current status of devices and drivers
> - Bind and unbind devices to different drivers
>
> Future extensions will be to make dpdk-pmdinfo.py, cpu_layout.py and
> dpdk-setup.sh more automation friendly.
Hi,
I'm not sure what you mean by an "interactive tool", since devbind contains
no menus or interactive prompts. It's a commandline tool driven by
parameters passed - in the same way as ethtool, ip, and various other
standard Linux tools. I personally use it regularly in scripts, e.g. the
rc.local script on my test system to automatically adjust bindings on boot.
That being said, I can see why someone might want a rest tool to query and
adjust these settings, I'm just not sure if DPDK is the best place to host
such scripts. Would that functionality not be better built into other
existing tools for configuring and managing systems?
Regards,
/Bruce
next prev parent reply other threads:[~2020-03-04 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 7:11 Muhammad Ahmad
2020-03-04 13:59 ` Bruce Richardson [this message]
2020-03-04 16:09 ` Stephen Hemminger
2020-03-12 9:03 ` Muhammad Ahmad
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=20200304135919.GB285@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=muhammad.ahmad@emumba.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 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).