From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: Luca Boccassi <lboccass@brocade.com>, dev <dev@dpdk.org>,
Stefan Bader <stefan.bader@canonical.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] SDK: Add scripts to initialize DPDK runtime
Date: Thu, 12 Jan 2017 15:43:24 +0200 [thread overview]
Message-ID: <CAATJJ0LfApetTjxw_ua9D7_i_g42vebk_msTcovhWnt+75jmiw@mail.gmail.com> (raw)
In-Reply-To: <3810875.kgVK3RKdmy@xps13>
On Mon, Dec 19, 2016 at 4:15 PM, Thomas Monjalon <thomas.monjalon@6wind.com>
wrote:
> Thanks for sending your Debian/Ubuntu work.
>
> 2016-12-13 16:47, Luca Boccassi:
> > From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> >
> > A tools/init directory is added with dpdk-init, a script that can be
> > used to initialize a DPDK runtime environment. 2 config files with
> > default options, dpdk.conf and interfaces, are provided as well
> > together with a SysV init script and a systemd service unit.
>
> I have 2 concerns:
>
> - What does exactly mean "initialize a DPDK runtime environment"?
> Should it be documented somewhere?
>
Sorry for the late reply, Luca made me aware that this was lost in the
Christmas hole.
It means that you make a system config ready to be used in a persistent way
e.g. cross reboots.
The common steps to prep a system in that regard are assigning a set of
cards to dpdk (=>dpdk-devbind) and furthermore to set up hugepages as
needed.
The latter is only a simple helper for the convenience of the admin. It can
suit 95% of the cases but if someone has something very specific in mind a
manual hugepage setup might be needed.
The conf files themself have comment on their usage.
I'm not sure how much more (on top of the comments in the config files) a
doc might be useful.
But then that might just be because I happen to know about that stuff.
We could hapilly copy the bit we have about it at
https://help.ubuntu.com/16.04/serverguide/DPDK.html#dpdk-config-dev
https://help.ubuntu.com/16.04/serverguide/DPDK.html#dpdk-config-hp
Luca/Thomas - what do you think about that?
> - Is it deprecating dpdk-setup.sh?
>
dpdk-setup is a one-shot effort and provides very different things.
the init script is for the system lifecycle, to be controlled by config
files and invoked automatically.
ATM - we covered what is needed on a regular base in the script, while
dpdk-setup has a longer list of use-cases.
If anybody identifies functions of dpdk-setup which would be reasonable in
a lifecycle management we should be open to take patches moving those from
the one-shot to the system service.
Also one could think of sharing some code between them - like providing
sourcable shell fragment that both scripts use to execute - yet I don't
think it is needed until I see a reasonable call that this is needed or
helpful.
Once (I don't expect that) all functionality would have moved it would be
deprecated, but not for now in my Opinion.
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
next prev parent reply other threads:[~2017-01-12 13:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 19:24 [dpdk-dev] [PATCH] " Luca Boccassi
2016-12-12 21:12 ` Bruce Richardson
2016-12-12 21:58 ` Luca Boccassi
2016-12-13 7:00 ` Christian Ehrhardt
[not found] ` <22e6b726-79f5-5c2b-2cc6-b11fba6384c7@canonical.com>
2016-12-13 15:19 ` Christian Ehrhardt
2019-01-17 17:38 ` Stephen Hemminger
2019-01-18 15:04 ` Ferruh Yigit
2016-12-12 23:41 ` Jay Rolette
2016-12-13 16:47 ` [dpdk-dev] [PATCH v2] " Luca Boccassi
2016-12-19 14:15 ` Thomas Monjalon
2017-01-12 13:43 ` Christian Ehrhardt [this message]
2017-03-16 18:13 ` Thomas Monjalon
2017-03-22 19:15 ` Luca Boccassi
2019-01-17 17:22 ` Ferruh Yigit
2017-09-18 20:44 ` Ferruh Yigit
2017-09-19 5:42 ` Christian Ehrhardt
2023-06-08 16:45 ` Stephen Hemminger
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=CAATJJ0LfApetTjxw_ua9D7_i_g42vebk_msTcovhWnt+75jmiw@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=lboccass@brocade.com \
--cc=stefan.bader@canonical.com \
--cc=thomas.monjalon@6wind.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).