Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Oct 2022 20:21:45 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 267060] net/dpdk:  error: too many arguments to function call, expected 3, have 4
Message-ID:  <bug-267060-7788-TWsIbopqZu@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-267060-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-267060-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267060

--- Comment #3 from Martin Filla <freebsd@sysctl.cz> ---
(In reply to Bruce Richardson from comment #2)
My FreeBSD setup is:=20
FreeBSD  13.1-RELEASE-p1 FreeBSD 13.1-RELEASE-p1 GENERIC amd64
and  dpdk20.11 is also without issue with poudriere. I am sorry

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D> Running Q/A tests (stage-qa)
=3D=3D=3D=3D> Checking for pkg-plist issues (check-plist)
=3D=3D=3D> Parsing plist
=3D=3D=3D> Checking for items in STAGEDIR missing from pkg-plist
=3D=3D=3D> Checking for items in pkg-plist which are not in STAGEDIR
=3D=3D=3D> No pkg-plist issues found (check-plist)
=3D>> Checking for staging violations... done
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<phase=
: package        >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D>  Building package for dpdk20.11-20.11.5
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D>> Recording filesystem state for preinst... done
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<phase=
: install        >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D>  Installing for dpdk20.11-20.11.5
=3D=3D=3D>  Checking if dpdk20.11 is already installed
=3D=3D=3D>   Registering installation for dpdk20.11-20.11.5
[freebsd13x64-default] Installing dpdk20.11-20.11.5...
The Intel(R) DPDK requires two kernel modules to be loaded in order to run.
To load these modules add loading lines to /boot/loader.conf

        contigmem_load=3D"YES"
        nic_uio_load=3D"YES"

The modules each take a number of parameters. These should be set in
loader.conf
before the above two lines to load the module.

* The "contigmem" module is used to reserve contiguous blocks of physical
memory
  for packet buffer use. It takes parameters for the number and size of blo=
cks
  to be reserved. An example is below, reserving a single 1G block:

        hw.contigmem.num_buffers=3D1
        hw.contigmem.buffer_size=3D1073741824

* The "nic_uio" module is used to expose the network card (NIC) hardware
  directly to userspace for use with the Intel(R) DPDK. If the NIC ports to=
 be
  used are in use by an existing driver, the nic_uio module can unbind the =
port
  from its existing driver when requested to do so. This is done by passing=
 the
  relevant PCI bus, device and function settings to the driver as parameter=
s.
  For example:

        hw.nic_uio.bdfs=3D"2:0:0,2:0:1"

=3D=3D=3D> SECURITY REPORT:

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267060-7788-TWsIbopqZu>