From: "Hunt, David" <david.hunt@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org, "dev@dpdk.org" <dev@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [dpdk-web] [PATCH v1] add dpdk-quickstart python script
Date: Thu, 25 Oct 2018 11:35:19 +0100 [thread overview]
Message-ID: <a1b2fcbe-27fe-6455-0811-af82209ae60e@intel.com> (raw)
In-Reply-To: <90623370.bXQ1XRRXSb@xps>
Hi Thomas,
On 25/10/2018 11:30 AM, Thomas Monjalon wrote:
> 25/10/2018 11:31, Hunt, David:
>> Hi Thomas,
>>
>>
>> On 25/10/2018 10:14 AM, Thomas Monjalon wrote:
>>> 25/10/2018 11:09, Hunt, David:
>>>> Hi,
>>>>
>>>> I'm just wondering if there is anything I can do to help move this
>>>> website patch forward? Any suggestions?
>>> The website has changed.
>>> It is using Hugo now.
>>> The update in doc/quick-start.html must be ported.
>> Sure, I'll have a look at that.
>>
>>> About the python script, I don't understand why you want to have it
>>> in the web repo?
>> The script needs to be somewhere outside the DPDK repo, browser
>> accessible (or wget, etc), so
>> the website archive seemed the most sensible place for it.
> Why outside of the repo?
> We can download files from the repo:
> wget http://git.dpdk.org/dpdk/plain/usertools/cpu_layout.py
Excellent, that's a very good suggestion. I'll make the necessary changes.
Also, the usertools directory seems to be a good place.
Thanks,
Dave.
>> So the idea was that the user gets the script, then when it's run, it
>> downloads DPDK,
>> installs package dependencies, builds DPDK, builds testpmd, binds to
>> NICs, and runs testpmd.
>>
>> Regards,
>> Dave.
>>
>>
>>>> On 3/8/2018 12:41 PM, david.hunt at intel.com (David Hunt) wrote:
>>>>> This patch contains two section.
>>>>> 1. Updates to the existing quick-start.html page giving
>>>>> infomration on the new dpdk-quickstart.py script.
>>>>> 2. The dpdk-quickstart.py script itself.
>>>>>
>>>>> 1. The Quick start section contains some instructions for
>>>>> building DPDK and running TestPMD.
>>>>> While this is still useful, automating these steps
>>>>> through a script would provide a much faster and painless
>>>>> way to have DPDK up and running. The new dpdk-quickstart.py
>>>>> aims to address this.
>>>>>
>>>>> 2. This script performs the following:
>>>>> - Gets the latest DPDK release
>>>>> - Gets the necessary dependencies (if needed)
>>>>> - Builds DPDK with the default target
>>>>> - Sets up hugepages
>>>>> - Helps the user to select the ports to use on DPDK
>>>>> - Runs TestPMD, showing packet forwarding between two ports
>>>>>
>>>>> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch at intel.com>
>>>>> Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko at intel.com>
>>>>> Signed-off-by: David Hunt <david.hunt at intel.com>
>>>>> ---
>>>>> doc/quick-start.html | 25 +
>>>>> scripts/dpdk-quickstart.py | 996 +++++++++++++++++++++++++++++++++++++
>>>>> 2 files changed, 1021 insertions(+)
>>>>> create mode 100755 scripts/dpdk-quickstart.py
>>>
>>>
>>
>
>
>
>
prev parent reply other threads:[~2018-10-25 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 11:41 [dpdk-dev] " David Hunt
2018-08-03 13:02 ` Burakov, Anatoly
2018-10-25 9:09 ` [dpdk-dev] [dpdk-web] " Hunt, David
2018-10-25 9:14 ` Thomas Monjalon
2018-10-25 9:31 ` Hunt, David
2018-10-25 10:30 ` Thomas Monjalon
2018-10-25 10:35 ` Hunt, David [this message]
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=a1b2fcbe-27fe-6455-0811-af82209ae60e@intel.com \
--to=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.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 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).