From: Thomas Monjalon <thomas@monjalon.net>
To: Sarosh Arif <sarosh.arif@emumba.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC] usertools: Replace dpdk-setup with a python curses based script
Date: Tue, 01 Sep 2020 15:30:50 +0200 [thread overview]
Message-ID: <2173565.OSGeAx7z5R@thomas> (raw)
In-Reply-To: <20200818100959.00fa004e@hermes.lan>
18/08/2020 19:09, Stephen Hemminger:
> On Tue, 18 Aug 2020 17:39:19 +0500
> Sarosh Arif <sarosh.arif@emumba.com> wrote:
>
> > dpdk-setup has been used for a long time in order to compile and
> > configure dpdk along with running some basic applications. dpdk-setup
> > uses the make build system to compile which is now deprecated. In addition
> > to this it has been discussed on the mailing list a few times that
> > dpdk-setup UI is quite old and it needs improvement along with
> > addition of some other facilities. This had created a need for python
> > curses based script that would provide similar functionality as
> > dpdk-setup but with more options and better UI. The idea is almost similar
> > to kernel's make menuconfig. The reason to select python curses is that it
> > comes as a standard library with python. The script will use the meson build
> > system for compilation.
> >
> > Here is a link containing suggested UI:
> > https://drive.google.com/file/d/18ngGpO_e-8FYNKjkKqS1IKQSrDDcXSO6/view?usp=sharing
> >
> > The following options will be present in the Menu and Sub-Menu:
> >
> > Compile
> > Compile with gcc
> > Compile with icc
> > Compile with clang
> > Compile examples
> > Cross compile
> > arm64_armada_linux_gcc
> > arm64_armv8_linux_gcc
> > arm64_bluefield_linux_gcc
> > arm64_dpaa_linux_gcc
> > arm64_emag_linux_gcc
> > arm64_n1sdp_linux_gcc
> > arm64_octeontx2_linux_gcc
> > arm64_stingray_linux_gcc
> > arm64_thunderx2_linux_gcc
> > Arm64_thunderx_linux_gcc
> > Ppc64le-power8-linux-gcc
> > cross-mingw
> > Hugepages
> > Setup hugepage for non-NUMA
> > Setup hugepages for NUMA
> > Remove hugepage mappings
> > Insert module
> > Setup VFIO permissions
> > VFIO
> > KNI
> > IBG UIO
> > Remove module
> > VFIO
> > KNI
> > IBG UIO
> > Bind and Unbind devices
> > Bind device to IGB UIO
> > Bind device to VFIO
> > Unbind devices from IGB UIO or VFIO driver
> > Display
> > Hugepages info
> > Current device settings
> > Run Applications
> > Test application → prompt user to enter flags and possibly build
> > directory name. Also give a default options for flags
> > Testpmd application → prompt user to enter flags and possibly
> > build directory name. Also give a default options for flags
> >
> > In addition to this, the user will have the facility to provide any
> > additional flags for compilation if he/she wishes to.
>
> I would prefer a set of scripts that each do one thing.
> Having a GUI is a lot of overhead to support.
Me too, I prefer simple scripts.
And I prefer even more documenting simple tasks.
We can extract the lines for hugepages settings in a standalone script.
Perhaps doing the same for VFIO setup.
Not sure about the rest.
next prev parent reply other threads:[~2020-09-01 13:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 12:39 [dpdk-dev] [RFC] usertools: Replace dpdk-setup with a python curses based script Sarosh Arif
2020-08-18 17:09 ` Stephen Hemminger
2020-09-01 13:30 ` Thomas Monjalon [this message]
2020-09-01 16:56 ` [dpdk-dev] [PATCH] usertools: add huge page setup script Stephen Hemminger
2020-09-02 9:47 ` Ferruh Yigit
2020-09-02 9:55 ` Bruce Richardson
2020-09-02 14:50 ` Stephen Hemminger
2020-09-03 22:48 ` [dpdk-dev] [PATCH v2] " Stephen Hemminger
2020-09-04 9:22 ` Bruce Richardson
2020-09-04 17:18 ` Stephen Hemminger
2020-09-04 14:58 ` Burakov, Anatoly
2020-09-04 15:10 ` Bruce Richardson
2020-09-04 18:35 ` [dpdk-dev] [PATCH] " Stephen Hemminger
2020-09-04 23:13 ` Ferruh Yigit
2020-09-04 23:30 ` Stephen Hemminger
2020-09-05 3:07 ` [dpdk-dev] [PATCH v4] " Stephen Hemminger
2020-09-06 3:42 ` [dpdk-dev] [PATCH v5] " Stephen Hemminger
2020-09-07 8:54 ` Ferruh Yigit
2020-09-07 8:58 ` Bruce Richardson
2020-09-07 17:20 ` Stephen Hemminger
2020-09-08 8:18 ` Bruce Richardson
2020-09-08 14:58 ` Stephen Hemminger
2020-09-08 21:49 ` Thomas Monjalon
2020-09-08 15:17 ` [dpdk-dev] [PATCH v6] usertools: add a " Stephen Hemminger
2020-09-09 11:46 ` Ferruh Yigit
2020-09-09 19:26 ` Ajit Khaparde
2020-09-09 18:51 ` [dpdk-dev] [PATCH v7] " Stephen Hemminger
2020-09-14 15:31 ` Burakov, Anatoly
2020-10-20 18:01 ` Ferruh Yigit
2020-11-22 21:39 ` Thomas Monjalon
2020-09-24 4:31 ` Stephen Hemminger
2020-11-22 21:30 ` Thomas Monjalon
2020-11-23 0:12 ` Stephen Hemminger
2020-11-24 17:45 ` Stephen Hemminger
2020-11-24 21:37 ` Thomas Monjalon
2020-11-25 9:16 ` Ferruh Yigit
2020-08-28 12:09 ` [dpdk-dev] [RFC] usertools: Replace dpdk-setup with a python curses based script Morten Brørup
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=2173565.OSGeAx7z5R@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=sarosh.arif@emumba.com \
--cc=stephen@networkplumber.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 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.