Hi, Tom,
epel-release is nothing but some yum repo files, so technically it should not
bring any code for dependencies. So it should be removed from runtime
dependencies for sure IMO. The reason is, we want to stick with whatever RedHat
supports. When we bring in epel-release, the RPMs that we
Jerome,
python3 is an implicit dependency of vpp-devel and I am not sure why.
Because of that I put python36 explicitly in Requires because I was
concerned about cross versions of Python between 34 and 36 having side
affects.
As for epel-release, it is harmless but is not strictly required
Congratulations Maciek & the CSIT team as well as the greater FD.io
communities.
Well done!
-daw-
On 5/10/2019 1:46 PM, Maciek Konstantynowicz (mkonstan) via Lists.Fd.Io
wrote:
Hi All,
FD.io CSIT-1904 report has been published on FD.io docs site:
html:
TLDR: Hopefully arm issues are resolved so jobs should correctly verify (they
work in sandbox, production test still running)
Two different issues:
JNLP connect failures: cause unconfirmed but certainly I was seeing latency
issues between jenkins slave and master varying between
1ms and
On 05/10/2019 12:46 PM, Benoit Ganne (bganne) wrote:
I verified it on CentOS 7.6 and it works fine: Here i s my gist for Robert
and Fred with the steps I used.
https://gist.github.com/tfherbert/64cef832f03935c6a2a58729718a36ff
Glad to hear, thanks a lot.
In CentOS 7.6, for RDMA drivers to
On 05/10/2019 12:46 PM, Benoit Ganne (bganne) wrote:
I verified it on CentOS 7.6 and it works fine: Here i s my gist for Robert
and Fred with the steps I used.
https://gist.github.com/tfherbert/64cef832f03935c6a2a58729718a36ff
Glad to hear, thanks a lot.
In CentOS 7.6, for RDMA drivers to
> There was no dmesg output from the run, and the strace output is here:
> https://gist.github.com/robertstarmer/826fd02d7255e6e5d322fa0a59fed182
For dmesg, you may need to run it under sudo (root) too to get the output
(security!).
Looking at the strace output (lines 6243-6254) it looks like
Hi All,
FD.io CSIT-1904 report has been published on FD.io docs site:
html: https://docs.fd.io/csit/rls1904/report/
pdf: https://docs.fd.io/csit/rls1904/report/_static/archive/csit_rls1904.pdf
Many thanks to All in CSIT, VPP and FD.io community who contributed and
worked hard to make CSIT-1904
> I verified it on CentOS 7.6 and it works fine: Here i s my gist for Robert
> and Fred with the steps I used.
> https://gist.github.com/tfherbert/64cef832f03935c6a2a58729718a36ff
Glad to hear, thanks a lot.
> In CentOS 7.6, for RDMA drivers to work, we need to install rdma rpm as I
> did in my
Ben,
I verified it on CentOS 7.6 and it works fine: Here i s my gist for
Robert and Fred with the steps I used.
https://gist.github.com/tfherbert/64cef832f03935c6a2a58729718a36ff
In CentOS 7.6, for RDMA drivers to work, we need to install rdma rpm as
I did in my 19.02 patch to get the
Hi Robert,
That could be an issue with /dev/infiniband/* access rights.
Could you share the output of:
~# echo "create int rdma host-if enp94s0f1 name mlx5" > rdma.vpp
~# sudo timeout 10 strace /usr/bin/vpp "unix { nodaemon exec $PWD/rdma.vpp }
plugins { plugin dpdk_plugin.so { disable } }"
~#
> Current versions of Mellanox DPDK do not require OFED.
> With a recent DPDK > 18.05 and recent kernel all you need is the rdma core
> library.
Sure but VPP 18.04 was mentioned (based on DPDK 18.02 AFAIK) among the
versions, plus I am unsure about CentOS/RHEL rdma-core version, so w/o more
On 05/10/2019 10:53 AM, Stephen Hemminger wrote:
On Fri, 10 May 2019 12:49:51 +
"Benoit Ganne (bganne) via Lists.Fd.Io" wrote:
I guess you are relying on DPDK here. Are you able to use the card with DPDK
testpmd?
If not, you may be missing Mellanox OFED driver, depending upon DPDK
On Fri, 10 May 2019 12:49:51 +
"Benoit Ganne (bganne) via Lists.Fd.Io" wrote:
> I guess you are relying on DPDK here. Are you able to use the card with DPDK
> testpmd?
> If not, you may be missing Mellanox OFED driver, depending upon DPDK version.
> Otherwise you can switch to VPP 19.04 and
Ben,
I had this working with 19.02 with my patch using dpdk driver with rdma.
https://gerrit.fd.io/r/#/c/18521/
Which I used in the rpms for CentOS.
The challenge I had was that convincing dpdk to "see" the pci,
That was because the server boots with the mlx ints in a bond and after
Jerome,
Let me take a look at this today. I will submit a patch to take them out
if I can verify that they are not needed.
--Tom
On 05/10/2019 05:11 AM, Jerome Tollet (jtollet) wrote:
Hi Thomas,
In https://gerrit.fd.io/r/#/c/18953/ you are putting epel-release and
Python3 into the
I guess you are relying on DPDK here. Are you able to use the card with DPDK
testpmd?
If not, you may be missing Mellanox OFED driver, depending upon DPDK version.
Otherwise you can switch to VPP 19.04 and use the new native driver:
https://gerrit.fd.io/r/c/19364/3/src/plugins/rdma/rdma_doc.md
Hi guys,
I’m having varied results with compiling VPP for use with Mellanox ConnectX 5
drivers.
I have one ubuntu 18.04 box that compiled VPP 18.10 without problems and runs a
Mellanox ConnectX 5 card without problems, however:
I have several machines that are fitted with ConnextX 4 cards
Copying Neale. He may not respond immediately since he's on PTO until May 13th.
HTH... Dave
-Original Message-
From: vpp-dev@lists.fd.io On Behalf Of Andreas Schultz
Sent: Friday, May 10, 2019 5:54 AM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] finding a virtual memory leak in VPP
Am Do., 9. Mai 2019 um 19:59 Uhr schrieb Dave Barach (dbarach)
:
>
> $ cat /proc//maps
>
>
>
> You could also start vpp under gdb and set a breakpoint in mmap...
uhm, that lead to something unexpected:
Breakpoint 1, __GI___mmap64 (addr=0x0, len=33554432, prot=3, flags=34,
fd=-1, offset=0) at
Hi Thomas,
In https://gerrit.fd.io/r/#/c/18953/ you are putting epel-release and Python3
into the dependencies.
1. I can understand that those are needed as BuildRequires:, but are they
really needed for Requires: ?
2. Why do we need epel-release as runtime requirement?
3. Do we
Hi Thomas,
I just pushed a small doc:
https://gerrit.fd.io/r/c/19364/3/src/plugins/rdma/rdma_doc.md
> I also tried:
> vpp# create interface rdma name mlx5
> create interface rdma: invalid interface (only mlx5 supported for now)
You are missing the 'host-if ' stanza, eg:
vpp# create int rdma
22 matches
Mail list logo
