From: Stephen Hemminger <stephen@networkplumber.org>
To: Hui Ling <kelvin.brookletling@gmail.com>
Cc: Andrew Bainbridge <andbain@microsoft.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK mlx4 PMD on Azure VM
Date: Mon, 8 Jan 2018 07:42:28 -0800 [thread overview]
Message-ID: <20180108074228.515774ea@xeon-e3> (raw)
In-Reply-To: <CAPNMKd4vpeeDbeNs=bWbrf9Hs1P0TaTVCduxscTabptYNQhp8w@mail.gmail.com>
On Mon, 8 Jan 2018 11:01:09 +0800
Hui Ling <kelvin.brookletling@gmail.com> wrote:
> Stephen,
>
> My last VM (DS3 v2, with 4 cores and 16GB memory) is in Canada East
> and I got AN enabled on my subscription so AN worked just fine.
>
> For DPDK, I saw from your slides in DPDK submit last year saying
> current DPDK solution in Azure needs:
>
> 1) Linux kerlnel 4.14
You need transparent bonding support which is in kernel netvsc driver.
It has been backported to Ubuntu Azure (4.13) package, RHEL 7 and SLES.
> 2) 8 cores
>
> I am not sure if these are must. I tried to upgrade my Ubuntu to 4.14,
> but then I ran into compilation issues with DPDK 17.11 for MLX4 PMD.
> So I stayed with older version of kernel for Ubuntu 16.04.
> With my config of VM, however, I could not get the failsafe.sh I got
> from MS for azure to work.
The number of cores requirement has been dropped, think it is available
with 4 now.
next prev parent reply other threads:[~2018-01-08 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 7:14 Hui Ling
2017-12-19 15:47 ` Thomas Monjalon
2017-12-19 16:22 ` Thomas Monjalon
2017-12-19 16:29 ` Ophir Munk
2017-12-20 2:00 ` Hui Ling
2017-12-20 13:39 ` Andrew Bainbridge
2017-12-21 7:35 ` Hui Ling
2018-01-02 4:27 ` Stephen Hemminger
2018-01-05 20:45 ` Stephen Hemminger
2018-01-08 3:01 ` Hui Ling
2018-01-08 15:42 ` Stephen Hemminger [this message]
2018-04-10 8:40 ` Hui Ling
2018-04-13 12:47 ` Andrew Bainbridge
2018-04-13 14:50 ` Hui Ling
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=20180108074228.515774ea@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=andbain@microsoft.com \
--cc=kelvin.brookletling@gmail.com \
--cc=users@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).