All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Luca Boccassi <lboccass@brocade.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: dev@dpdk.org, stefan.bader@canonical.com, bruce.richardson@intel.com
Subject: Re: [PATCH v2] SDK: Add scripts to initialize DPDK runtime
Date: Mon, 19 Dec 2016 15:15:26 +0100	[thread overview]
Message-ID: <3810875.kgVK3RKdmy@xps13> (raw)
In-Reply-To: <1481647672-9187-1-git-send-email-lboccass@brocade.com>

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?

- Is it deprecating dpdk-setup.sh?

  reply	other threads:[~2016-12-19 14:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 19:24 [PATCH] SDK: Add scripts to initialize DPDK runtime 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 ` [PATCH v2] " Luca Boccassi
2016-12-19 14:15   ` Thomas Monjalon [this message]
2017-01-12 13:43     ` Christian Ehrhardt
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=3810875.kgVK3RKdmy@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=bruce.richardson@intel.com \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dev@dpdk.org \
    --cc=lboccass@brocade.com \
    --cc=stefan.bader@canonical.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.