[Bug 1539775] [NEW] Enable ppc64el on dpdk

[bugproxy]

Public bug reported:

== Comment: #0 - Fernando Seiti Furusato <***@br.ibm.com> - 2016-01-27 14:00:13 ==
Although package dpdk is not listed on Architectures and fails to build, a fix can enable it.
It just needs little adjustments to the build and it builds successfully.

I am attaching a .debdiff with a suggested fix.

Thanks

** Affects: ubuntu
Importance: Undecided
Assignee: Taco Screen team (taco-screen-team)
Status: New


** Tags: architecture-ppc64le bugnameltc-136144 severity-medium targetmilestone-inin1604

** Tags added: architecture-ppc64le bugnameltc-136144 severity-medium
targetmilestone-inin1604
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1539775/+subscriptions

[bugproxy]

Default Comment by Bridge

** Attachment added: "patch enabling ppc64 on dpdk"
https://bugs.launchpad.net/bugs/1539775/+attachment/4559423/+files/dpdk-ppc64el.debdiff

** Changed in: ubuntu
Assignee: (unassigned) => Taco Screen team (taco-screen-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1539775/+subscriptions

[Gary Gaydos]

** Package changed: ubuntu => dpdk (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[Fernando Seiti Furusato]

Hello Christian.
This is exactly the same as 1538664 because I created this immediately after invalidating the other one.
Please consider this as the feature request.

Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

So all I said on the other bug still applies.
Everbody is invited to use my ppa for testing purpose, but since dpdk is going to be in main in 16.04 we would need someone to commit seriously on testing and working on dodk-ppc64el.

For that I need the taco Team and IBM to coordinate if/how it shall be
done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

------- Comment From ***@br.ibm.com 2016-02-05 06:26 EDT-------
Hello.

I have downloaded the source from Christian's dpdk from ppa, built and
installed it from [1].

Just tried to run a dpdk_proc_info and got the following:

# dpdk_proc_info
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 8 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 2 lcore(s)
PANIC in rte_eal_config_attach():
Cannot open '/var/run/.rte_config' for rte_mem_config
6: [/lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xb4) [0x3fff804d3734]]
5: [/lib/powerpc64le-linux-gnu/libc.so.6(+0x23500) [0x3fff804d3500]]
4: [dpdk_proc_info(main+0x1b4) [0x1000797c]]
3: [/usr/lib/powerpc64le-linux-gnu/libdpdk.so.0(rte_eal_init+0x1044) [0x3fff80937924]]
2: [/usr/lib/powerpc64le-linux-gnu/libdpdk.so.0(__rte_panic+0x80) [0x3fff808f0684]]
1: [/usr/lib/powerpc64le-linux-gnu/libdpdk.so.0(rte_dump_stack+0x40) [0x3fff80958460]]
Aborted

I also tried running the test from the quick-start page [2], but since I
used debian packaging, I tried and used testpmd built there. Not sure if
this is correct:

# ./debian/build/shared-root/app/testpmd -c7 -n3 --vdev=eth_pcap0,iface=eth0 --vdev=eth_pcap1,iface=eth1 -- -i --nb-cores=2 --nb-ports=2 --total-num-mbufs=2048
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 8 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 2 lcore(s)
EAL: lcore 2 unavailable
EAL: invalid coremask

[1] https://launchpad.net/~paelzer/+archive/ubuntu/dpdk-merge-2.2
[2] http://dpdk.org/doc/quick-start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

** Tags removed: targetmilestone-inin1604
** Tags added: targetmilestone-inin1610
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

** Changed in: dpdk (Ubuntu)
Status: New => Triaged

** Changed in: dpdk (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[Mathew Hodson]

** Changed in: dpdk (Ubuntu)
Milestone: None => ubuntu-16.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Hi,
I've seen upstream ppc work recently.
So I wanted to know whats your status on testing/stability and so on?

We are working on dpdk 16.04 currently - is ppc something we
should/could consider now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

** Tags removed: targetmilestone-inin1610
** Tags added: targetmilestone-inin1704
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[Fernando Seiti Furusato]

Hi Christian.

My apologies for not replying to this earlier.
I will try to check how it is on our side and let you know.

Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[Breno Leitão]

Hello, I have been working internally and we want to enable and support
DPDK on Ubuntu. Is it still possible to enable it to be compiled against
ppc64el?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Hi,
it is kind of late for 16.10 I think.
Since I lack HW to test it - as already made aware before in this bug -
this depends to some extend on your commitment to validate and test.
If I enable it in a ppa tomorrow are you willing and able to test that ppa
Tue-Friday to ensure that DPDK and Vswitch-DPDK is working on ppc64el?

In that case I think we could make this an FFE bug I prep it for you and
given your (=IBMs) commitment to test and jointly support this should have
a chance to pass.
The chance to break anything on the other architectures is very low due to
that.

Please confirm me that until tomorrow and I shall prepare something for you
that we can work on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[Mark Brown]

Folks, we should not consider this a "wishlist" so much as a "why isn't
this already in Power since we are claiming equivalent support for
features". This also blocks some of our NFV market.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

------- Comment From ***@us.ibm.com 2016-08-29 17:42 EDT-------
A few clarifications that I would like to add for Ubuntu 16.10 :

-support for DPDK (on Power) will be in conjunction with MLNX_OFED
-It will be Tech Preview only
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Hi Pradeep and Breno,
since you refer to MLNX_OFED I assume that implies you will need the mlx4/5 pmd drivers in DPDK.
Those drivers are disabled by default in DPDK which usually implies they are not considered is not stable to be used. In this case they are disabled due to external dependencies. But never the less that implies they get less exposure to testing and discussions, not to speak about the potential version mismatches that often occur with mlx based drivers.

Also DPDK for power can only build for power8 and I'm not sure if that
gets us into trouble. I asked around and got confirmations that recent
userspace is on >=power8 anyway. So at least that won't be an issue
then.

As I promised I started to prepare something for you in a ppa that you can test to verify - as this will be the first step to think about going on with a feature freeze exception in case you really want to push for inclusion into yakkety.
To do so, I have:
- enabled dpdk for ppc64el
- added power arch dependent custom target and conf
- enabled mlx
- added dependencies for mlx
- enabled autopkgtests for ppc64el

Almost as I expected that fails to build for the MLX drivers. And given that http://www.mellanox.com/page/products_dyn?product_family=209&mtag=pmd_for_dpdk refers to only DPDK 2.2 and not 16.07.
I explicitly checked - that also applies to power, see https://launchpadlibrarian.net/281700914/buildlog_ubuntu-yakkety-ppc64el.dpdk_16.07-0ubuntu3~dev02_BUILDING.txt.gz
These issues are known http://dpdk.org/ml/archives/dev/2015-November/027781.html
But I can't really think of providing a in-archive package build against out-of archive Mellanix OFED libs on that short term. Maybe there is a way, but for now that means mlx drivers stay disabled.

But with those disabled ppc64el has issues. It FTBFS as-is where amd64, i386 and arm64 just work.
https://launchpadlibrarian.net/281703816/buildlog_ubuntu-yakkety-ppc64el.dpdk_16.07-0ubuntu3~dev03_BUILDING.txt.gz

The ppa (would be) at: https://launchpad.net/~paelzer/+archive/ubuntu/deb-dpdk-16.07
For now only with associated build issues and log there.
The git branch where I have done that is at: https://code.launchpad.net/~ubuntu-server/dpdk/+git/dpdk/+ref/enablepowerpc

Please feel free to take a look at the branch yourself if you like to
give it an extra try, just as we worked together in the past.

I've not yet given up considering to enable it, but given the state as reported that certainly is worth a bit of a discussion and a lot more work.
If you want tech preview only anyway, how about keeping it a ppa for 16.10 - that gives you time to identify and fixup the arch specific issues?

Mid Term - I encourage you work with me early on to get it into
https://wiki.fd.io/view/Deb_dpdk - from there it will naturally migrate
into 17.04 later on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

@Mark - thanks for your feedback about the prio.
In fact we have discussed here and on IRC about DPDK for Power for quite a while.
I wouldn't mind setting any higher priority, but so far the bug was never blocked on us and wishlist reflected the "somewhen in the future when upstream ppc is ready" state this was in for quite a while.

Given it was re-requested now - despite all the issues I found - and
also by your referral on power-NFV market opportunities I'll raise the
prio.

** Changed in: dpdk (Ubuntu)
Importance: Wishlist => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

I consider the ppc build issue a task of IBM to look into, but took the
chance to researched the case of the MLX issues a bit.

I found bugs that would address this, but aren't fixed due to people changing at mellanox that were supposed to work on this.
To get the MLX drivers working we are blocked on (at least):
https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1528799
https://bugs.launchpad.net/ubuntu/+source/libmlx4/+bug/1528790
https://bugs.launchpad.net/ubuntu/+source/libmlx5/+bug/1528795

There are more like these to update all in sync to each other, but those three in particular block MLX for DPDK.
That now being known I'd at least nack to enabling MLX drivers in DPDK for Yakkety.

If you can work without MLX PMD DPDK drivers please go further and try
to check why testpmd is failing for ppc64el only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

** Tags removed: bugnameltc-136144 severity-medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

** Tags added: bugnameltc-136144 severity-medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

Default Comment by Bridge

** Attachment added: "patch enabling ppc64 on dpdk"
https://bugs.launchpad.net/bugs/1539775/+attachment/4731956/+files/dpdk-ppc64el.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Hi,
this is just the "old" patch we had in the past isn't it?
It still refers to 2.0, libdpdk0 and many other things long gone, has no ref to any current PMD packages and so on.

Also these days you shouldn't need to patch default vars, you have your own.
We set machines and such via d/rules as needed and I did so in my branch already along other changes for you. Also with all that in place it searches already the correct defconfig_ppc_64-power8-linuxapp-gcc already, no need to copy-patch that.

As I suggested the git branch I listed before [1] should be the base for your work now.
No offense, but looking just attached patch I have to assume you haven't even looked at the pre-work I did for you.
I did a few more tweaks for you in that branch, but the main issue I reported still exists [3] and [4].
Please branch off this, get it working in regard to [2] and report your branch as merge request to mine. There I can review the changes and discuss/apply as appropriate.

Please catch me as cpaelzer on IRC if you want a faster turnaround time
or schedule a meeting.

[1]: https://code.launchpad.net/~ubuntu-server/dpdk/+git/dpdk/+ref/enablepowerpc
[2]: https://launchpadlibrarian.net/281703816/buildlog_ubuntu-yakkety-ppc64el.dpdk_16.07-0ubuntu3~dev03_BUILDING.txt.gz
[3]: https://launchpad.net/~paelzer/+archive/ubuntu/deb-dpdk-16.07/+packages
[4]: https://launchpadlibrarian.net/282056793/buildlog_ubuntu-yakkety-ppc64el.dpdk_16.07-0ubuntu3~dev04_BUILDING.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

------- Comment From ***@in.ibm.com 2016-09-01 23:10 EDT-------
Regarding build error reported for ppc64el as in dev03 and dev 04 builds:
https://launchpad.net/~paelzer/+archive/ubuntu/deb-dpdk-16.07

Removing "CONFIG_RTE_LIBRTE_PMD_BOND=n" from config/
defconfig_ppc_64-power8-linuxapp-gcc should help us proceeding
further. so, dpdk.spec needs this change.

You would also need to patch .debian/ as below:

--- dpdk-16.07.org/debian/librte-eal2.symbols 2016-08-30 02:40:26.000000000 -0400
+++ dpdk-16.07/debian/librte-eal2.symbols 2016-08-31 06:13:52.365436013 -0400
@@ -122,6 +122,7 @@ librte_eal.so.2 librte-eal2 #MINVER#
***@DPDK_2.0 16.04
***@DPDK_2.0 16.04
(arch=!arm64)***@DPDK_16.07 16.07~rc3
+ (arch=!ppc64el)***@DPDK_16.07 16.07~rc3
***@DPDK_2.0 16.04
***@DPDK_2.0 16.04
***@DPDK_2.0 16.04

--- dpdk-16.07.org/debian/control 2016-08-31 09:36:22.063819444 -0400
+++ dpdk-16.07/debian/control 2016-08-31 09:37:42.760626875 -0400
@@ -131,7 +131,7 @@ Depends: ${misc:Depends},
librte-pmd-vhost1 (= ${binary:Version}),
librte-pmd-virtio1 (= ${binary:Version}),
librte-pmd-vmxnet3-uio1 (= ${binary:Version}),
- librte-pmd-xenvirt1 (= ${binary:Version}),
+ librte-pmd-xenvirt1 (= ${binary:Version}) [amd64 arm64 i386],
librte-port3 (= ${binary:Version}),
librte-power1 (= ${binary:Version}),
librte-reorder1 (= ${binary:Version}),

--- dpdk-16.07.org/debian/dpdk.conf 2016-08-30 02:40:26.000000000 -0400
+++ dpdk-16.07/debian/dpdk.conf 2016-08-31 09:49:40.299580656 -0400
@@ -6,6 +6,13 @@
# NR_2M_PAGES=64
#
+# The number of 16M hugepages to reserve on system boot
+#
+# Default is 0
+# To e.g. let it reserve 32x 16M Hugepages set:
+# NR_16M_PAGES=64
+
+#
# The number of 1G hugepages to reserve on system boot
#
# Default is 0

--- dpdk-16.07.org/debian/dpdk-init 2016-08-30 02:40:26.000000000 -0400
+++ dpdk-16.07/debian/dpdk-init 2016-08-31 09:30:26.288573196 -0400
@@ -124,6 +124,9 @@ mount_hugetlbfs() {
if [ -n "${NR_2M_PAGES}" -a -z "" ]; then
_mount_hugetlbfs 2M
fi
+ if [ -n "${NR_16M_PAGES}" -a -z "" ]; then
+ _mount_hugetlbfs 16M
+ fi
if [ -n "${NR_1G_PAGES}" -a -z "" ]; then
_mount_hugetlbfs 1G
fi
@@ -166,6 +169,7 @@ setup_hugepages() {
. /etc/dpdk/dpdk.conf
_setup_hugepages "hugepages-2048kB" "$NR_2M_PAGES"
+ _setup_hugepages "hugepages-16384kB" "$NR_16M_PAGES"
_setup_hugepages "hugepages-1048576kB" "$NR_1G_PAGES"

# dpdk uses 2*#hugepages mappings, increase for huge systems LP #1507921

I can build dpdk packages successfully following above changes. I just need to
get familiar with your enablepowerpc branch on your git. Considering round trip
time I need to push above changes, can I request you to apply changes as above
and share us .deb for dpdk.

Btw, could you please also share IRC group name and server to join chat
with you.

Thanks,
Gowrishankar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Hi,
I doubt a spec file will help deb packaging, but I can still use that info :-)
You changes look good, I was able to apply and extended them for you.
Some of that as-is would have broken arm or the dep8 tests.

Regarding this change:
Removing "CONFIG_RTE_LIBRTE_PMD_BOND=n" from config/
Could you get that upstream for power, so that this doesn't have to be a delta for a long time?

A test on your machines should be done with dpdk - 16.07-0ubuntu3~dev05
from ppa: https://launchpad.net/~paelzer/+archive/ubuntu/deb-dpdk-16.07

If you could confirm that this works for you I'd try to integrate and push to deb_dpdk and Yakkety.
FYI - The latter will also need a FFE to pass.

And the irc name - as I wrote - is cpaelzer. Sorry if that could be misread.
I'm in many channels on freenode, you can go with #deb_dpdk or #ubuntu-server in this case I think.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

------- Comment From ***@in.ibm.com 2016-09-02 06:28 EDT-------
Thanks. Strangely, I am seeing xenvirt1 pmd still a dependent lib for libdpdk-dev.

$ sudo apt-get install libdpdk-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libdpdk-dev : Depends: librte-pmd-xenvirt1 (= 16.07-0ubuntu3~dev05) but it is not installable
E: Unable to correct problems, you have held broken packages.

I would need libdpdk-dev to install dpdk.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

------- Comment From ***@in.ibm.com 2016-09-02 07:14 EDT-------
I downloaded your PPA source to check debian/control if supported arch included for librte-pmd-xenvirt1 as I proposed. The change was there.

librte-pmd-xenvirt1 (= ${binary:Version}) [amd64 arm64 i386],

But then, as I manually start to "debuild -us -uc -b" and get .deb
built, I observe that, those arch entries are removed in debian/control
after debuild completes. I could not understand due to which step in
debuild it gets removed. Could you please throw some hints ?

librte-pmd-xenvirt1 (= ${binary:Version}),

Consequently, I end up seeing same error if I try to install locally
built libdpdk-dev :

dpkg: dependency problems prevent configuration of libdpdk-dev:ppc64el:
libdpdk-dev:ppc64el depends on librte-pmd-xenvirt1 (= 16.07-0ubuntu3~dev05); however:
Package librte-pmd-xenvirt1 is not installed.

Once I corrected this control file to include those arch for librte-pmd-
xenvirt1, I could able to locally build packages and install libdpdk-dev
(and hence dpdk and other packages) successfully. Could you please check
on your end.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Hi,
the issue with the xenvirt dep was a weird one. After some analysis I could track it down to a build artifact from a change to dpdk packaging a few weeks ago that made it into the uploaded tarballs. That was hard to spot.

I fixed that up and after that also found a few other related creeping
issues that I was able to fix. The latest upload in the ppa is at
version 16.07-0ubuntu3~dev07 and I hope it should be good now for your
test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[Breno Leitão]

Hello Christian,

Thanks. I will ask Pradeep, who is our DPDK specialist, to test it.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Hi,
thanks for testing, sad that there could have been no HW test and also that it was only testpmd.
I think it is time to discuss what we do about your request to have it as "tech preview only".

To my knowledge there is no such thing as a tech preview per package
(please correct me if I'm wrong). It either is of good quality and will
go into the package and be supported for the full support period or it
is not - in which case it should not go in.

I'd currently prefer to decline the inclusion for the following reasons:
- power8 dpdk upstream work is still on the old state of dpdk 2.2 (see the example with the broken default config)
- power still disables many devices since they are not tested properly
- the devices you requested yourself (mlx) are actually unusable in a Distribution environment
- there is not a lot of test exposure on power yet, nor upstream focus

If we would put it into 16.10 archive as is this would mean
Canonical will have to
- Add the delta to packaging
- add release notes entry about "tech preview" only status
- carry changes into deb_dpdk packaging
But if we do so, that implies several todos and especially serious commitment for IBM
- stabilize dpdk on power upstream
- take over responsibility the power related issues for the 16.10 support time

I'm afraid if we pick it up now it might end up carrying this as
"preview" forever and it will become a maintenance burden.

As suggested before, given the current release deadlines and the current state as outline I'd suggest we provide a ppa which provides dpdk as in Ubuntu 16.10 plus the ppc enablement I created.
- This much more matches what a "tech preview" is and despite not in the main archive still gives everyone an established way to consume it.
- On that you can work, experiment and test
- Avoids throwing things out later which is a much higher impact task
- Once stability and confidence is reached we can enable it in the main archive in e.g. 17.04


Looking forward for your opinion on "providing it as a ppa for 16.10".
If it is unacceptable I can provide the packaging bits as they are done, but you will have to convince the release team in the discussion for the feature freeze exception which surely will hit this topic.

If you are good with a ppa let me know and I'll do all that is needed including bringing the packaging to deb_dpdk as well.
But if you are really hard bound on going into 16.10 I'd ask you to add the content for the FFE process right away so we don't loose time -> https://wiki.ubuntu.com/FreezeExceptionProcess.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

------- Comment From ***@in.ibm.com 2016-09-07 05:49 EDT-------
Thank you Christian. I have verified your dev07 deb for dpdk using testpmd on top of virtio pmd for packet forwarding sanity.

***@ubu1610-0830:~$ sudo testpmd -c 0xf -d /usr/lib/powerpc64le-linux-gnu/librte_pmd_virtio.so -- -i
EAL: Detected 32 lcore(s)
EAL: Probing VFIO support...
EAL: PCI device 0000:00:08.0 on NUMA socket -1
EAL: probe driver: 1af4:1000 rte_virtio_pmd
EAL: PCI device 0000:00:09.0 on NUMA socket -1
EAL: probe driver: 1af4:1000 rte_virtio_pmd
Interactive-mode selected
USER1: create a new mbuf pool <mbuf_pool_socket_0>: n=171456, size=2176, socket=0
Configuring Port 0 (socket 0)
Port 0: 52:54:C0:A2:7C:43
Configuring Port 1 (socket 0)
Port 1: 52:54:C0:A2:7C:44
Checking link statuses...
Port 0 Link Up - speed 10000 Mbps - full-duplex
Port 1 Link Up - speed 10000 Mbps - full-duplex
Done
testpmd> start
io packet forwarding - ports=2 - cores=1 - streams=2 - NUMA support disabled, MP over anonymous pages disabled
Logical Core 1 (socket 0) forwards packets on 2 streams:
RX P=0/Q=0 (socket 0) -> TX P=1/Q=0 (socket 0) peer=02:00:00:00:00:01
RX P=1/Q=0 (socket 0) -> TX P=0/Q=0 (socket 0) peer=02:00:00:00:00:00

io packet forwarding - CRC stripping disabled - packets/burst=32
nb forwarding cores=1 - nb forwarding ports=2
RX queues=1 - RX desc=128 - RX free threshold=0
RX threshold registers: pthresh=0 hthresh=0 wthresh=0
TX queues=1 - TX desc=512 - TX free threshold=0
TX threshold registers: pthresh=0 hthresh=0 wthresh=0
TX RS bit threshold=0 - TXQ flags=0xf00
testpmd> stop
Telling cores to stop...
Waiting for lcores to finish...

---------------------- Forward statistics for port 0 ----------------------
RX-packets: 857474 RX-dropped: 0 RX-total: 857474
TX-packets: 433345 TX-dropped: 98 TX-total: 433443
----------------------------------------------------------------------------

---------------------- Forward statistics for port 1 ----------------------
RX-packets: 433443 RX-dropped: 0 RX-total: 433443
TX-packets: 853543 TX-dropped: 3931 TX-total: 857474
----------------------------------------------------------------------------

+++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
RX-packets: 1290917 RX-dropped: 0 RX-total: 1290917
TX-packets: 1286888 TX-dropped: 4029 TX-total: 1290917
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Done.
testpmd> quit

Shutting down port 0...
Stopping ports...
Done
Closing ports...
Done

Shutting down port 1...
Stopping ports...
Done
Closing ports...
Done

Bye...
***@ubu1610-0830:~$ uname -a
Linux ubu1610-0830 4.4.0-9136-generic #55-Ubuntu SMP Fri Aug 26 05:56:24 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

***@ubu1610-0830:~$ cat /etc/issue
Ubuntu Yakkety Yak (development branch) \n \l

Above sanity was done with Yakkety kvm guest running dpdk, due to some
issues I am facing to setup yakkety on a baremetal. If the above test is
fine, could you please integrate your changes and release dpdk in
yakkety ?. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

------- Comment From ***@us.ibm.com 2016-09-08 21:05 EDT-------
(In reply to comment #33)

A big thank you for your help with in moving this forward. Appreciate
all the effort that has gone into it.

Hopefully I can answer several of your questions and alleviate your
concerns. First let me paint the overall picture and answer some of the
specifics later.

Our team has been active in the community for a few months and have been
submitting several patches to bring Power on par with other
architectures. In fact just today we got an ack for one of the
outstanding issues. That should clear the way for acceptance of the
entire patch set upstream.

Right now our focus is the Mellanox adapter and that is why we requested
support in Ubuntu 16.10 with MLNX_OFED. We hope to be able to remove
that limitation in a future Ubuntu release. If it is acceptable, we
would like to suggest the following steps:

1. Start with Ubuntu 16.10 Tech Preview and support only Mellanox adapter (requires MLNX_OFED)
2. In Ubuntu 17.04 expand the Tech Preview to include additional adapters
3. Lift the Tech preview in 17.10

That should hopefully erase some of the concerns and ease acceptance. We
are committed to supporting DPDK on Power.

Post by ChristianEhrhardt
Hi,
thanks for testing, sad that there could have been no HW test and also that
it was only testpmd.

We have been working with upstream DPDK 16.07 and have locally tested
ip_pipeline and other tests as well. We have tested the LPM and ACL
libraries as well. Once the patches go upstream (as mentioned
previously), these can be pulled into Ubuntu 16.10 as well.

One of the things we discovered during the course of our testing is that
package ovs-dpdk has not been enabled on Power in the ppa.

Post by ChristianEhrhardt
I think it is time to discuss what we do about your request to have it as
"tech preview only".
To my knowledge there is no such thing as a tech preview per package (please
correct me if I'm wrong). It either is of good quality and will go into the
package and be supported for the full support period or it is not - in which
case it should not go in.

The Tech Preview request is only for DPDK on Power in Ubuntu 16.10.
Previous responses should help ease your concerns.

Post by ChristianEhrhardt
- power8 dpdk upstream work is still on the old state of dpdk 2.2 (see the
example with the broken default config)

We have been working with upstream DPDK 16.07 as mentioned

Post by ChristianEhrhardt
- power still disables many devices since they are not tested properly
- the devices you requested yourself (mlx) are actually unusable in a
Distribution environment

I understand some of your concerns. It is precisely to facilitate
thorough testing that we are requesting a Tech Preview. The request is
to release note it with a "Tech Preview" label only for the Mellanox
devices. In this way, a customer will not attempt to use other devices.

Post by ChristianEhrhardt
- there is not a lot of test exposure on power yet, nor upstream focus
If we would put it into 16.10 archive as is this would mean
Canonical will have to
- Add the delta to packaging
- add release notes entry about "tech preview" only status
- carry changes into deb_dpdk packaging
But if we do so, that implies several todos and especially serious
commitment for IBM
- stabilize dpdk on power upstream
- take over responsibility the power related issues for the 16.10 support
time

Yes, we do understand the commitment required from IBM and previous
responses should provide the assurance you are seeking.

Post by ChristianEhrhardt
I'm afraid if we pick it up now it might end up carrying this as "preview"
forever and it will become a maintenance burden.

The previous suggestion provides a roadmap for DPDK availability on
Ubuntu (on Power)

Post by ChristianEhrhardt
As suggested before, given the current release deadlines and the current
state as outline I'd suggest we provide a ppa which provides dpdk as in
Ubuntu 16.10 plus the ppc enablement I created.
- This much more matches what a "tech preview" is and despite not in the
main archive still gives everyone an established way to consume it.
- On that you can work, experiment and test
- Avoids throwing things out later which is a much higher impact task
- Once stability and confidence is reached we can enable it in the main
archive in e.g. 17.04

Given the previous explanations, can you move these to the main archive?
That would be our preference. This will also enable additional run time
outside of IBM. Please let us know what you think, and what are the next
steps moving forward.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Hi,
thanks for your reply - it improved my expectation a bit, but not in all regards.
I'll slim down the content of the discussion a bit and try to focus on the important pieces.

Post by bugproxy
1. Start with Ubuntu 16.10 Tech Preview and support only Mellanox

adapter (requires MLNX_OFED)

As I explained before - the mlx pmd drivers in dpdk can't be built.
This can't be fixed in DPDK (well it might be), but the right solution is getting Mellanox to properly upstream their bits into libverbs and such.

Post by bugproxy
2. In Ubuntu 17.04 expand the Tech Preview to include additional adapters
3. Lift the Tech preview in 17.10
That should hopefully erase some of the concerns and ease acceptance.

We are committed to supporting DPDK on Power.


I like the step by step approach in general and I trust you in your commitment - thanks!

Post by bugproxy
One of the things we discovered during the course of our testing is that package ovs-dpdk has not been enabled on Power in the ppa.

I can add that to the ppa, but this is just one more example of this likely isn't ready.
Openvswitch has no enablement for dpdk on ppc yet. I can add it for you, and provide it in the ppa but I highly doubt we want to make that change as well so lat in the cycle.

Post by bugproxy
I understand some of your concerns. It is precisely to facilitate thorough testing that we are requesting a Tech Preview. The request is to release note it with a "Tech Preview" label only for the Mellanox devices. In this way, a customer will not attempt to use other devices.

I was at IBM long enough to know the Tech Preview business - I just haven't found a Ubuntu way of doing this for "parts of a package".
I mean it is easy to have let's say a package "ppc-special-tool-X" as preview.
But dpdk and more so openvswitch are in main and important - and I can't easily make different support statements per arch afaik.

Post by bugproxy

Post by ChristianEhrhardt
- take over responsibility the power related issues for the 16.10 support
time

Yes, we do understand the commitment required from IBM and previous

responses should provide the assurance you are seeking.


Thank you, that is one thing I wanted to hear.

Post by bugproxy
Given the previous explanations, can you move these to the main archive? That would be our preference. This will also enable additional run time outside of IBM. Please let us know what you think, and what are the next steps moving forward.

Yes I think working together we could put it in the archive, but not in 16.10 with all you wanted.
The following can't be met:
- dpdk mlx pmd drivers which can't be made available
- I doubt you'll get the openvswitch dpdk enablement on ppc64el that late either

That said you have two options:
A)
- enable ppc64el in dpdk in 16.10
- without MLX drivers
- without changing openvswitch
- the impact to other architectures should be zero, but one can never be sure
- drive a FFE very late in the cycle
- on such a short runway I expect issue to show up which will be unnecessary work and bad publicity for both of us

B)
- enable ppc64el in dpdk in 16.10 via a ppa
- without MLX drivers initially
- but if you later on can provide a DPDK patch that lets it build with upstream libibverb I surely can add them to the ppa
- also provide a dpdk ppc64el enabled openvswitch to the same ppa
- the impact to other architectures now IS zero
- the ppa is what makes it a "tech preview" IMO
- here it is perfectly fine to add custom patches/fixes if needed
- do not consider ppa a bad thing, many projects have "official ppa's" and many people use packages from ppa's on a daily base.

For both options we would then go on:
- Right when 17.04 opens up we will
- enable dpdk on ppc64el
- enable dpdk support on ppc64el in openvswitch
- If we get things reasonably stable 17.04 will be all fine and released with it
- if things are bad, we identify roadblocks, anybody looses funding or anything like it we can disable them again before 17.04 is released

I clearly prefer B). Because A) will leave you without any dpdk exploiters (ovs) and without the device drivers you wanted in 16.10.
That might only be worth if that was on someones scorechart, but not for any real use by a customer or tester.
B clearly is better for everyone as it has all you need in 16.10 as a ppa and we can work on 17.04 together (earlier than after feature freeze this time) to get it in proper shape to be in the release itself.

If you, despite all tries to explain why B is better than A still want A
- could you please tell me what the benefit of A would be over B? I
really would like to see that, but I don't so far.

You asked for next steps:
- Next step if you choose A is that you add a https://wiki.ubuntu.com/FreezeExceptionProcess here in the bug to convince the release Team.
- Next step if you chose B (and I hope you do) is give me a few days to enable dpdk/ppc in openvswitch for you as well, I'll modify the bug here accordingly for all further things needed towards 17.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

------- Comment From ***@us.ibm.com 2016-09-09 23:55 EDT-------
Your hesitation is understandable. The level of support expected is probably different in our individual perceptions. I would also like to clear up a few things because there maybe some miscommunication.

The first step in supporting DPDK on Power, the plan was to support
Mellanox adapters only. This is with MLNX_OFED. That implies the
Mellanox drivers and PMD will come from Mellanox and not Canonical.
Hopefully that explains the rationale for the request.

However, given the hesitation to turn on OVS-DPDK (in the main archive)
and the need for an FFE etc, etc, would make this plan impractical.

For 16.10 let us go with plan B) as you suggest. We will get involved
early in the process for 17.04 and that should ease things. Thanks you
for your support!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Thank you Pradeep,

Thanks for the clarification about the MLX drivers.
I'm a bit afraid that this will just be another drop on spinning the "mlx-often-broken-by-being-too-special" wheel instead of once getting them upstream for real and by that to "just work". But that is a debate outside of the scope of ppc64el&dpdk.

I went ahead and worked on B) right away.
After a bunch of build issues that blocked me at first I added an dpdk enabled openvswitch to the ppa at https://launchpad.net/~paelzer/+archive/ubuntu/deb-dpdk-16.07

Along that I found a few more issues in the dpdk ppc64el packaging but
was able to fix them.

Also I already pushed the enablement of ppc to the shared packaging we drive at https://wiki.fd.io/view/Deb_dpdk.
That will help to get you onto Debian as well and to drop Ubuntu delta for this in 17.04.

I'm leaving the bug open until 17.04 opens up, dpdk gets added there and
and we start working together in regard to ppc64el enablement, testing
and verification.

** Changed in: dpdk (Ubuntu)
Milestone: ubuntu-16.10 => ubuntu-17.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

------- Comment From ***@in.ibm.com 2016-09-13 10:58 EDT-------
Thanks Christian for the update.

We have got our platform enabled now to include missing libs like lpm,
acl and others as well. These are essential for applications relying on
them including some of sample applications in dpdk-doc. Could you please
let us know if you would prefer yourself taking changes directly from
dpdk master (commits below) or want us to merge these in ~ubuntu-
server/dpdk/+git/dpdk/+ref/enablepowerpc repo.

* 58d55fd examples/ip_pipeline: fix lcore mapping for ppc64
* 81f713e config: enable packet framework on ppc64le
* 43f15e2 table: fix verification on hash bucket header alignment
* 46fbbf3 sched: enable on ppc64le
* f2379ca examples/l3fwd: add AltiVec for ppc64
* 1d73135 acl: add AltiVec for ppc64
* d2cc795 lpm: add AltiVec for ppc64

I just seek your opinion to go forward in these scenarios, in future as
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Hi,
just to confirm - I understand those are upstream patches to dpdk that got
in past dpdk 16.07 right, but you'd want those in the ppa and later in
Ubuntu 17.04 right?

In regard to the process, tor now and the near future future I think the
process should be that you try to create patches on top of
https://gerrit.fd.io/r/#/q/refs/heads/deb_dpdk_16.07
Naturally at some point in time that will be a further dpdk version, but
for now that is it 16.07.
This is part of https://wiki.fd.io/view/Deb_dpdk

As I suggested before feel free to catch me as "cpaelzer" on irc if you
want any assistance or guidance to do so.
I'm also one of the people on the other end that reviews and merges the
patches you send there.

From there I can always spin off and upload to the ppa I opened up as well

as later serve into 17.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

I wanted to let you know, that I've made the latest changes available for you.
The ppa now holds dpdk - 16.07-1~git2 which contains the contributions of your coworker gshankarmk.

I also pushed a newer version of openvswitch openvswitch -
2.6.0~git20160912.dc61b4e-0ubuntu5~ppa1 including the ppc enablement I
already had before but on that newer openvswitch version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

------- Comment From ***@us.ibm.com 2016-09-26 10:25 EDT-------
Great, thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Upload which has it enabled is in the queue, waiting for one more
approval and then a rebuild of openvswitch - but ppc enabled dpdk is
there now https://launchpad.net/ubuntu/+source/dpdk/16.11-1.

I'll ping you again once it is consumable.

** Changed in: dpdk (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

if [ -n "${NR_2M_PAGES}" -a -z "$(get_hugetlbfs_mountpoint '2M')" ]; then
+ if [ -n "${NR_16M_PAGES}" -a -z "$(get_hugetlbfs_mountpoint '16M')" ]; then
if [ -n "${NR_1G_PAGES}" -a -z "$(get_hugetlbfs_mountpoint '1G')" ]; then
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

What ?

It has the 16M code we discussed a while ago in its init script:
grep 16 debian/dpdk-init
if [ -n "${NR_16M_PAGES}" -a -z "$(get_hugetlbfs_mountpoint '16M')" ]; then
_mount_hugetlbfs 16M
_setup_hugepages "hugepages-16384kB" "$NR_16M_PAGES"

Is there an issue with it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Since release is correctly in queue but blocked due to the component
mismatch for now setting back from released to committed to reflect
that.

** Changed in: dpdk (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[Manoj Iyer]

Assigning to paelzer since he has this bug already fix committed.

** Changed in: dpdk (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => ChristianEhrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Hi,
I got the issues fixed that prevented it from migrating.
Now fixed in https://launchpad.net/ubuntu/+source/dpdk/16.11-1ubuntu3

ppc build fine
https://launchpad.net/ubuntu/+source/dpdk/16.11-1ubuntu3/+build/11981275

The auto-close in the changelog got lost in the back and forth between
sync and merge of the package, thereby closing manually now.

** Changed in: dpdk (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Let me clarify:
- dpdk is hereby enabled for ppc64el
- dpdk is not yet enabled for openvswitch-switch-dpdk for ppc64el

If you happen to need the second as well, please get in touch asap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[ChristianEhrhardt]

Please do note that I happened to find that openvswitch rebuilt fine as well but there ppc is not enabled for DPDK.
See: https://launchpad.net/ubuntu/+source/openvswitch/2.6.1-0ubuntu4

There was no bug about that, so no one considered enabling that as well so far.
If you want/need that as well please let us know asap (FF on 16th).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

------- Comment From ***@in.ibm.com 2017-02-09 06:25 EDT-------
New request for openvswitch-switch-dpdk to be in main archive:

https://bugs.launchpad.net/ubuntu/+source/openvswitch-dpdk/+bug/1663206

** Tags removed: bugnameltc-136144 severity-medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions

[bugproxy]

** Tags added: bugnameltc-136144 severity-medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539775

Title:
Enable ppc64el on dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1539775/+subscriptions