2015-01-02 09:07, Lyn M:
> In my original post, I thought my choice of hex portmask -p 0x3 was causing
> this issue -- now I know that was not the case. But, I am still curious
> about how the hex portmask is determined. Since I only have two ports
> bound to igb_uio, my hex postmask will always
On Tue, Jan 06, 2015 at 10:02:25AM +0100, Thomas Monjalon wrote:
> 2015-01-02 09:07, Lyn M:
> > In my original post, I thought my choice of hex portmask -p 0x3 was causing
> > this issue -- now I know that was not the case. But, I am still curious
> > about how the hex portmask is determined. Sin
On 1/2/2015 11:08 PM, Lyn M wrote:
> Neil, your patch works. I am now able to run testpmd, as well as l3fwd
> with DPDK 1.8.0 and CONFIG_RTE_BUILD_COMBINE_LIBS=y. Thank you much!
>
> In my original post, I thought my choice of hex portmask -p 0x3 was causing
> this issue -- now I know that was no
On Fri, Jan 02, 2015 at 09:07:40AM -0600, Lyn M wrote:
> Neil, your patch works. I am now able to run testpmd, as well as l3fwd
> with DPDK 1.8.0 and CONFIG_RTE_BUILD_COMBINE_LIBS=y. Thank you much!
>
I'll post it for official review shortly.
> In my original post, I thought my choice of hex po
Neil, your patch works. I am now able to run testpmd, as well as l3fwd
with DPDK 1.8.0 and CONFIG_RTE_BUILD_COMBINE_LIBS=y. Thank you much!
In my original post, I thought my choice of hex portmask -p 0x3 was causing
this issue -- now I know that was not the case. But, I am still curious
about h
On Wed, Dec 31, 2014 at 10:37:45PM -0500, Neil Horman wrote:
> On Wed, Dec 31, 2014 at 10:50:10AM -0600, Lyn M wrote:
> > Neil,
> > When I build DPDK 1.8.0 with the default value
> > CONFIG_RTE_BUILD_COMBINE_LIBS=n,
> > I am able to run the testpmd successfully. So, that does appear to be the
> >
On Wed, Dec 31, 2014 at 10:50:10AM -0600, Lyn M wrote:
> Neil,
> When I build DPDK 1.8.0 with the default value
> CONFIG_RTE_BUILD_COMBINE_LIBS=n,
> I am able to run the testpmd successfully. So, that does appear to be the
> culprit.
> The objdump -t output for testpmd (with COMBINE_LIBS=n and CO
Neil,
When I build DPDK 1.8.0 with the default value CONFIG_RTE_BUILD_COMBINE_LIBS=n,
I am able to run the testpmd successfully. So, that does appear to be the
culprit.
The objdump -t output for testpmd (with COMBINE_LIBS=n and COMBINE_LIBS=y)
files are here:
https://www.dropbox.com/sh/6os9yfn22jj
On Wed, Dec 31, 2014 at 08:18:34AM -0600, Lyn M wrote:
> Neil, to build DPDK, I am doing the following steps:
> 1) download DPDK tarball (1.7.1 or 1.8.0) from
> http://dpdk.org/browse/dpdk/refs/
> 2) untar
> 3) edit config/common_linuxapp and change CONFIG_RTE_BUILD_COMBINE_LIBS
> from "n" to "y"
>
Neil, to build DPDK, I am doing the following steps:
1) download DPDK tarball (1.7.1 or 1.8.0) from
http://dpdk.org/browse/dpdk/refs/
2) untar
3) edit config/common_linuxapp and change CONFIG_RTE_BUILD_COMBINE_LIBS
from "n" to "y"
4) follow all of the steps in http://dpdk.org/doc/quick-start
When
On Tue, Dec 30, 2014 at 12:54:17PM -0600, Lyn M wrote:
> Neil, thank you for your reply.
>
> I used the DPDK 8.1.0 setup.sh script to clean the system (unbind NICs,
> rmmod igb_uio and uio, remove hugepage mappings), and then re-built for
> x86_64-native-linuxapp-gcc, setup hugepages, insmod the m
Neil, thank you for your reply.
I used the DPDK 8.1.0 setup.sh script to clean the system (unbind NICs,
rmmod igb_uio and uio, remove hugepage mappings), and then re-built for
x86_64-native-linuxapp-gcc, setup hugepages, insmod the modules, bound the
NICs, but have the same result when trying to r
On Mon, Dec 29, 2014 at 02:18:09PM -0600, Lyn M wrote:
> Hello all,
>
> Rangeley platform (1 CPU with 8 cores, 4x1 GbE, 2x10 GbE, Intel PCIe card
> with 2x10 GbE fiber)
> FC20 with hugepages enabled
> DPDK 1.8.0 built with T=x86_64-ivshmem-linuxapp-gcc
>
> */usr/src/dpdk/tools/dpdk_nic_bind.py -
Hello all,
Rangeley platform (1 CPU with 8 cores, 4x1 GbE, 2x10 GbE, Intel PCIe card
with 2x10 GbE fiber)
FC20 with hugepages enabled
DPDK 1.8.0 built with T=x86_64-ivshmem-linuxapp-gcc
*/usr/src/dpdk/tools/dpdk_nic_bind.py --status*
Network devices using DPDK-compatible driver
=
14 matches
Mail list logo