|
Revision tags: v24.07-rc2, v24.07-rc1, v24.03, v24.03-rc4, v24.03-rc3, v24.03-rc2, v24.03-rc1, v23.11, v23.11-rc4, v23.11-rc3, v23.11-rc2, v23.11-rc1, v23.07, v23.07-rc4, v23.07-rc3, v23.07-rc2, v23.07-rc1, v23.03, v23.03-rc4, v23.03-rc3, v23.03-rc2, v23.03-rc1 |
|
| #
f62d5262 |
| 07-Dec-2022 |
Junxiao Shi <git@mail1.yoursunny.com> |
net/memif: change socket listener owner uid/gid
This allows a DPDK application running with root privilege to create a memif socket listener with non-root owner uid and gid, which can be connected f
net/memif: change socket listener owner uid/gid
This allows a DPDK application running with root privilege to create a memif socket listener with non-root owner uid and gid, which can be connected from client applications running without root privilege.
Signed-off-by: Junxiao Shi <git@mail1.yoursunny.com> Acked-by: Stephen Hemminger <stephen@networkplumber.org> Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
show more ...
|
|
Revision tags: v22.11, v22.11-rc4, v22.11-rc3, v22.11-rc2, v22.11-rc1 |
|
| #
4851ef2b |
| 28-Jul-2022 |
David Marchand <david.marchand@redhat.com> |
bus/vdev: make driver-only headers private
The vdev bus interface is for drivers only. Mark as internal and move the header in the driver headers list.
While at it, cleanup the code: - fix indentat
bus/vdev: make driver-only headers private
The vdev bus interface is for drivers only. Mark as internal and move the header in the driver headers list.
While at it, cleanup the code: - fix indentation, - remove unneeded reference to bus specific singleton object, - remove unneeded list head structure type, - reorder the definitions and macro manipulating the bus singleton object, - remove inclusion of rte_bus.h and fix the code that relied on implicit inclusion,
Signed-off-by: David Marchand <david.marchand@redhat.com> Acked-by: Rosen Xu <rosen.xu@intel.com> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
show more ...
|
|
Revision tags: v22.07, v22.07-rc4, v22.07-rc3, v22.07-rc2, v22.07-rc1, v22.03, v22.03-rc4, v22.03-rc3, v22.03-rc2, v22.03-rc1 |
|
| #
b6c0f464 |
| 09-Feb-2022 |
Weiguo Li <liwg06@foxmail.com> |
net/memif: remove pointer deference before null check
There are duplicates of assignment here, the one before null check may cause a null pointer deference, so remove the previous one.
Fixes: 09c7e
net/memif: remove pointer deference before null check
There are duplicates of assignment here, the one before null check may cause a null pointer deference, so remove the previous one.
Fixes: 09c7e63a71f9 ("net/memif: introduce memory interface PMD") Cc: stable@dpdk.org
Signed-off-by: Weiguo Li <liwg06@foxmail.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
show more ...
|
| #
7be78d02 |
| 29-Nov-2021 |
Josh Soref <jsoref@gmail.com> |
fix spelling in comments and strings
The tool comes from https://github.com/jsoref
Signed-off-by: Josh Soref <jsoref@gmail.com> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
|
|
Revision tags: v21.11, v21.11-rc4, v21.11-rc3, v21.11-rc2 |
|
| #
aedd054c |
| 01-Nov-2021 |
Harman Kalra <hkalra@marvell.com> |
drivers: check interrupt file descriptor validity
This patch fixes coverity issue by adding a check for negative value to avoid bad bit shift operation and other invalid use of file descriptors.
Co
drivers: check interrupt file descriptor validity
This patch fixes coverity issue by adding a check for negative value to avoid bad bit shift operation and other invalid use of file descriptors.
Coverity issue: 373717, 373697, 373685 Coverity issue: 373723, 373720, 373719, 373718, 373715, 373714, 373713 Coverity issue: 373710, 373707, 373706, 373705, 373704, 373701, 373700 Coverity issue: 373698, 373695, 373692, 373690, 373689 Coverity issue: 373722, 373721, 373709, 373702, 373696 Fixes: d61138d4f0e2 ("drivers: remove direct access to interrupt handle")
Signed-off-by: Harman Kalra <hkalra@marvell.com> Acked-by: Haiyue Wang <haiyue.wang@intel.com> Acked-by: David Marchand <david.marchand@redhat.com>
show more ...
|
|
Revision tags: v21.11-rc1 |
|
| #
d61138d4 |
| 22-Oct-2021 |
Harman Kalra <hkalra@marvell.com> |
drivers: remove direct access to interrupt handle
Removing direct access to interrupt handle structure fields, rather use respective get set APIs for the same. Making changes to all the drivers acce
drivers: remove direct access to interrupt handle
Removing direct access to interrupt handle structure fields, rather use respective get set APIs for the same. Making changes to all the drivers access the interrupt handle fields.
Signed-off-by: Harman Kalra <hkalra@marvell.com> Acked-by: Hyong Youb Kim <hyonkim@cisco.com> Signed-off-by: David Marchand <david.marchand@redhat.com> Tested-by: Raslan Darawsheh <rasland@nvidia.com>
show more ...
|
| #
295968d1 |
| 22-Oct-2021 |
Ferruh Yigit <ferruh.yigit@intel.com> |
ethdev: add namespace
Add 'RTE_ETH' namespace to all enums & macros in a backward compatible way. The macros for backward compatibility can be removed in next LTS. Also updated some struct names to
ethdev: add namespace
Add 'RTE_ETH' namespace to all enums & macros in a backward compatible way. The macros for backward compatibility can be removed in next LTS. Also updated some struct names to have 'rte_eth' prefix.
All internal components switched to using new names.
Syntax fixed on lines that this patch touches.
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Tyler Retzlaff <roretzla@linux.microsoft.com> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru> Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Acked-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Wisam Jaddo <wisamm@nvidia.com> Acked-by: Rosen Xu <rosen.xu@intel.com> Acked-by: Chenbo Xia <chenbo.xia@intel.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: Somnath Kotur <somnath.kotur@broadcom.com>
show more ...
|
| #
18627ced |
| 28-Sep-2021 |
Junxiao Shi <git@mail1.yoursunny.com> |
net/memif: allocate socket hash on any NUMA socket
Previously, memif socket hash is always allocated on NUMA socket 0. If the application is entirely running on another NUMA socket and EAL --socket-
net/memif: allocate socket hash on any NUMA socket
Previously, memif socket hash is always allocated on NUMA socket 0. If the application is entirely running on another NUMA socket and EAL --socket-limit prevents memory allocation on NUMA socket 0, memif creation fails with "HASH: memory allocation failed" error.
This patch allows allocating memif socket hash on any NUMA socket.
Signed-off-by: Junxiao Shi <git@mail1.yoursunny.com> Reviewed-by: Jakub Grajciar <jgrajcia@cisco.com>
show more ...
|
|
Revision tags: v21.08, v21.08-rc4, v21.08-rc3, v21.08-rc2 |
|
| #
4e30586d |
| 23-Jul-2021 |
Nathan Skrzypczak <nathan.skrzypczak@gmail.com> |
net/memif: fix abstract socket address length
This fixes using abstract sockets with memifs. We were not passing the exact addr_len, which requires zeroing the remaining sun_path and doesn't appear
net/memif: fix abstract socket address length
This fixes using abstract sockets with memifs. We were not passing the exact addr_len, which requires zeroing the remaining sun_path and doesn't appear well in other utilities (e.g. lsof -U)
Signed-off-by: Nathan Skrzypczak <nathan.skrzypczak@gmail.com> Reviewed-by: Jakub Grajciar <jgrajcia@cisco.com>
show more ...
|
|
Revision tags: v21.08-rc1, v21.05, v21.05-rc4, v21.05-rc3, v21.05-rc2, v21.05-rc1, v21.02, v21.02-rc4, v21.02-rc3, v21.02-rc2 |
|
| #
df96fd0d |
| 29-Jan-2021 |
Bruce Richardson <bruce.richardson@intel.com> |
ethdev: make driver-only headers private
The rte_ethdev_driver.h, rte_ethdev_vdev.h and rte_ethdev_pci.h files are for drivers only and should be a private to DPDK and not installed.
Signed-off-by:
ethdev: make driver-only headers private
The rte_ethdev_driver.h, rte_ethdev_vdev.h and rte_ethdev_pci.h files are for drivers only and should be a private to DPDK and not installed.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com> Acked-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Steven Webster <steven.webster@windriver.com>
show more ...
|
|
Revision tags: v21.02-rc1, v20.11, v20.11-rc5, v20.11-rc4, v20.11-rc3, v20.11-rc2, v20.11-rc1 |
|
| #
d250589d |
| 15-Oct-2020 |
Stephen Hemminger <stephen@networkplumber.org> |
net/memif: replace master/slave arguments
Replace master/slave terms in this driver.
The memory interface drivers uses a client/server architecture so change the variable names and device arguments
net/memif: replace master/slave arguments
Replace master/slave terms in this driver.
The memory interface drivers uses a client/server architecture so change the variable names and device arguments to that.
The previous devargs are maintained for compatibility, but if used cause a notice in the log.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
show more ...
|
| #
2f865ed0 |
| 12-Oct-2020 |
Jakub Grajciar <jgrajcia@cisco.com> |
net/memif: use abstract socket address
Abstract socket address has no connection with filesystem pathnames and the socket disappears once all open references are closed.
Memif pmd will use abstract
net/memif: use abstract socket address
Abstract socket address has no connection with filesystem pathnames and the socket disappears once all open references are closed.
Memif pmd will use abstract socket address by default. For backwards compatibility use new argument 'socket-abstract=no'
Signed-off-by: Jakub Grajciar <jgrajcia@cisco.com>
show more ...
|
|
Revision tags: v20.08, v20.08-rc4, v20.08-rc3, v20.08-rc2, v20.08-rc1, v20.05, v20.05-rc4, v20.05-rc3, v20.05-rc2, v20.05-rc1, v20.02, v20.02-rc4 |
|
| #
06123fdd |
| 19-Feb-2020 |
Július Milan <jmilan.dev@gmail.com> |
net/memif: fix init when already connected
This patch fixes the situation when there is already connected pair of memif interfaces and another slave tries to initiate the connection with (already oc
net/memif: fix init when already connected
This patch fixes the situation when there is already connected pair of memif interfaces and another slave tries to initiate the connection with (already occupied) master. Expected behavior is that the second slave is refused and gets disconnect message with reason: "Already connected", while old connection remains functional.
Fixes: 09c7e63a71f9 ("net/memif: introduce memory interface PMD") Cc: stable@dpdk.org
Signed-off-by: Július Milan <jmilan.dev@gmail.com> Reviewed-by: Jakub Grajciar <jgrajcia@cisco.com>
show more ...
|
| #
cbbbbd33 |
| 09-Mar-2020 |
Július Milan <jmilan.dev@gmail.com> |
net/memif: enable loopback
With this patch it is possible to connect 2 DPDK memifs into loopback, i.e. when they have the same id and different roles, as for example: "--vdev=net_memif0,role=maste
net/memif: enable loopback
With this patch it is possible to connect 2 DPDK memifs into loopback, i.e. when they have the same id and different roles, as for example: "--vdev=net_memif0,role=master,id=0" "--vdev=net_memif1,role=slave,id=0"
Signed-off-by: Július Milan <jmilan.dev@gmail.com> Reviewed-by: Jakub Grajciar <jgrajcia@cisco.com>
show more ...
|
|
Revision tags: v20.02-rc3, v20.02-rc2, v20.02-rc1, v19.11, v19.11-rc4, v19.11-rc3, v19.11-rc2 |
|
| #
43b815d8 |
| 04-Nov-2019 |
Jakub Grajciar <jgrajcia@cisco.com> |
net/memif: support zero-copy slave
Zero-copy slave support for memif PMD. Slave interface exposes DPDK memory to master interface. Only single file segments are supported (EAL option --single-file-s
net/memif: support zero-copy slave
Zero-copy slave support for memif PMD. Slave interface exposes DPDK memory to master interface. Only single file segments are supported (EAL option --single-file-segments).
Signed-off-by: Jakub Grajciar <jgrajcia@cisco.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
show more ...
|
|
Revision tags: v19.11-rc1 |
|
| #
d803feec |
| 23-Oct-2019 |
Jakub Grajciar <jgrajcia@cisco.com> |
net/memif: fix Unix domain address length
Define MEMIF_SOCKET_UN_SIZE to size of unix domain socket address. Report error in case of longer path.
Fixes: b923866c6974 ("net/memif: allow for full key
net/memif: fix Unix domain address length
Define MEMIF_SOCKET_UN_SIZE to size of unix domain socket address. Report error in case of longer path.
Fixes: b923866c6974 ("net/memif: allow for full key size in socket name")
Signed-off-by: Jakub Grajciar <jgrajcia@cisco.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
show more ...
|
|
Revision tags: v19.08, v19.08-rc4, v19.08-rc3, v19.08-rc2 |
|
| #
b923866c |
| 16-Jul-2019 |
Stephen Hemminger <stephen@networkplumber.org> |
net/memif: allow for full key size in socket name
The key size for memif is 256 but the unix domain socket structure has space for 100 bytes. Change it to use a larger buffer and not hard code the k
net/memif: allow for full key size in socket name
The key size for memif is 256 but the unix domain socket structure has space for 100 bytes. Change it to use a larger buffer and not hard code the keysize everywhere.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org> Tested-by: Jakub Grajciar <jgrajcia@cisco.com>
show more ...
|
| #
de4473d9 |
| 07-Aug-2019 |
Jerin Jacob <jerinj@marvell.com> |
net/memif: fix build with gcc 9.1
gcc-9 is stricter on NULL arguments for printf. Fix the following build error by avoiding NULL argument to printf.
In file included from drivers/net/memif/memif_so
net/memif: fix build with gcc 9.1
gcc-9 is stricter on NULL arguments for printf. Fix the following build error by avoiding NULL argument to printf.
In file included from drivers/net/memif/memif_socket.c:26: In function 'memif_socket_create', inlined from 'memif_socket_init' at net/memif/memif_socket.c:965:12: net/memif/rte_eth_memif.h:35:2: error: '%s' directive argument is null [-Werror=format-overflow=] 35 | rte_log(RTE_LOG_ ## level, memif_logtype, \ | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 36 | "%s(): " fmt "\n", __func__, ##args) | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Fixes: 09c7e63a71f9 ("net/memif: introduce memory interface PMD")
Signed-off-by: Jerin Jacob <jerinj@marvell.com>
show more ...
|
| #
10bd0ad5 |
| 05-Aug-2019 |
Jakub Grajciar <jgrajcia@cisco.com> |
net/memif: fix error paths
Coverity issue: 343440, 343459, 343464, 343394 Fixes: 09c7e63a71f9 ("net/memif: introduce memory interface PMD")
Signed-off-by: Jakub Grajciar <jgrajcia@cisco.com>
|
|
Revision tags: v19.08-rc1 |
|
| #
c41a0495 |
| 25-Jun-2019 |
Jakub Grajciar <jgrajcia@cisco.com> |
net/memif: support multi-process
Multi-process support for memif PMD. Primary process handles connection establishment. Secondary process queries for memory regions.
Signed-off-by: Jakub Grajciar <
net/memif: support multi-process
Multi-process support for memif PMD. Primary process handles connection establishment. Secondary process queries for memory regions.
Signed-off-by: Jakub Grajciar <jgrajcia@cisco.com> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
show more ...
|
| #
09c7e63a |
| 06-Jun-2019 |
Jakub Grajciar <jgrajcia@cisco.com> |
net/memif: introduce memory interface PMD
Shared memory packet interface (memif) PMD allows for DPDK and any other client using memif (DPDK, VPP, libmemif) to communicate using shared memory. The cr
net/memif: introduce memory interface PMD
Shared memory packet interface (memif) PMD allows for DPDK and any other client using memif (DPDK, VPP, libmemif) to communicate using shared memory. The created device transmits packets in a raw format. It can be used with Ethernet mode, IP mode, or Punt/Inject. At this moment, only Ethernet mode is supported in DPDK memif implementation. Memif is Linux only.
Signed-off-by: Jakub Grajciar <jgrajcia@cisco.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
show more ...
|