Home
last modified time | relevance | path

Searched refs:dpdk (Results 1 – 25 of 218) sorted by relevance

123456789

/f-stack/lib/
H A Dff_config.c136 cfg->dpdk.nb_procs = count; in parse_lcore_mask()
341 cfg->dpdk.nb_ports = sz; in parse_port_list()
748 if (cfg->dpdk.no_huge) { in dpdk_args_setup()
751 if (cfg->dpdk.proc_mask) { in dpdk_args_setup()
759 if (cfg->dpdk.memory) { in dpdk_args_setup()
763 if (cfg->dpdk.proc_type) { in dpdk_args_setup()
786 if (cfg->dpdk.nb_vdev) { in dpdk_args_setup()
821 if (cfg->dpdk.nb_bond) { in dpdk_args_setup()
993 uint16_t lcore_id = cfg->dpdk.proc_lcore[cfg->dpdk.proc_id]; in ff_check_config()
1018 cfg->dpdk.proc_id = -1; in ff_default_config()
[all …]
H A Dff_dpdk_if.c190 nb_ports = ff_global_cfg.dpdk.nb_ports; in check_all_ports_link_status()
246 ff_global_cfg.dpdk.max_portid); in init_lcore_conf()
406 int nb_ports = ff_global_cfg.dpdk.nb_ports; in init_dispatch_ring()
528 nb_ports = ff_global_cfg.dpdk.nb_ports; in init_kni()
698 if (ff_global_cfg.dpdk.tso) { in init_port_start()
1048 if (ff_global_cfg.dpdk.nb_procs < 1 || in ff_dpdk_init()
1050 ff_global_cfg.dpdk.proc_id >= ff_global_cfg.dpdk.nb_procs || in ff_dpdk_init()
1051 ff_global_cfg.dpdk.proc_id < 0) { in ff_dpdk_init()
1053 ff_global_cfg.dpdk.nb_procs, in ff_dpdk_init()
1054 ff_global_cfg.dpdk.proc_id); in ff_dpdk_init()
[all …]
/f-stack/dpdk/doc/guides/howto/
H A Dlm_virtio_vhost_user.rst53 cd /root/dpdk/host_scripts
65 cd /root/dpdk/usertools
72 cd /root/dpdk/usertools
116 cd /root/dpdk/vm_scripts
146 cd /root/dpdk/usertools
153 cd /root/dpdk/usertools
419 /root/dpdk/usertools/dpdk-devbind.py --status
426 /root/dpdk/usertools/dpdk-devbind.py -b igb_uio 0000:00:03.0
427 /root/dpdk/usertools/dpdk-devbind.py -b igb_uio 0000:00:04.0
429 /root/dpdk/usertools/dpdk-devbind.py --status
[all …]
H A Dpacket_capture_framework.rst25 The :ref:`dpdk-pdump <pdump_tool>` tool is developed based on the
27 of enabling or disabling packet capture on DPDK ports. The ``dpdk-pdump`` tool
37 capture framework and acts as a server, and the ``dpdk-pdump`` tool acts as a
39 launched first, and then the ``dpdk-pdump`` tool. Packets from ``testpmd``
46 * The ``dpdk-pdump`` tool can only be used in conjunction with a primary
48 dpdk, only ``testpmd`` is modified to initialize packet capture framework,
49 other applications remain untouched. So, if the ``dpdk-pdump`` tool has to
55 * The ``dpdk-pdump`` tool depends on the libpcap based PMD.
69 Packet capturing on a DPDK port using the dpdk-pdump tool.
75 The following steps demonstrate how to run the ``dpdk-pdump`` tool to capture
[all …]
H A Dtelemetry.rst23 socket with path */var/run/dpdk/\*/dpdk_telemetry.v2* (when the primary process
49 ./app/dpdk-testpmd
53 ./usertools/dpdk-telemetry.py
57 Connecting to /var/run/dpdk/rte/dpdk_telemetry.v2
/f-stack/dpdk/usertools/
H A Dmeson.build5 'dpdk-devbind.py',
6 'dpdk-pmdinfo.py',
7 'dpdk-telemetry.py',
8 'dpdk-hugepages.py'
/f-stack/dpdk/
H A DMAINTAINERS28 T: git://dpdk.org/dpdk
33 T: git://dpdk.org/next/dpdk-next-net
37 T: git://dpdk.org/next/dpdk-next-net-brcm
41 T: git://dpdk.org/next/dpdk-next-net-intel
45 T: git://dpdk.org/next/dpdk-next-net-mrvl
49 T: git://dpdk.org/next/dpdk-next-net-mlx
54 T: git://dpdk.org/next/dpdk-next-virtio
58 T: git://dpdk.org/next/dpdk-next-crypto
67 T: git://dpdk.org/dpdk-stable
142 T: git://dpdk.org/dpdk
[all …]
/f-stack/dpdk/doc/guides/contributing/
H A Dstable.rst55 https://git.dpdk.org/dpdk-stable where bugfixes will be backported to.
67 the latest `stable roadmap <https://core.dpdk.org/roadmap/#stable>`_.
81 Fixes suitable for backport should have a ``Cc: stable@dpdk.org`` tag in the
89 Cc: stable@dpdk.org
94 Fixes not suitable for backport should not include the ``Cc: stable@dpdk.org`` tag.
108 The Stable and LTS release are coordinated on the stable@dpdk.org mailing
112 should also be CCed to the `stable@dpdk.org <https://mails.dpdk.org/listinfo/stable>`_
122 * Uploading a tarball of the release to dpdk.org.
123 * Sending an announcement to the `announce@dpdk.org <https://mails.dpdk.org/listinfo/announce>`_
126 Stable releases are available on the `dpdk.org download page <https://core.dpdk.org/download/>`_.
H A Dvulnerability.rst10 Only the main repositories (dpdk and dpdk-stable) of the core project
39 to `security@dpdk.org <https://core.dpdk.org/security#contact>`_.
43 <https://mails.dpdk.org/roster/security>`_.
76 <https://bugs.dpdk.org/buglist.cgi?f1=bug_group&o1=equals&v1=security>`_)
183 (`security-prerelease@dpdk.org <mailto:security-prerelease@dpdk.org>`_),
191 <https://mails.dpdk.org/roster/security-prerelease>`_), are:
195 have made the request to `techboard@dpdk.org <mailto:techboard@dpdk.org>`_
243 (`security-prerelease@dpdk.org <mailto:security-prerelease@dpdk.org>`_),
287 to `announce@dpdk.org <mailto:announce@dpdk.org>`_ and to `the public OSS-security
291 Patches are then sent to `dev@dpdk.org <mailto:dev@dpdk.org>`_
[all …]
H A Dpatches.rst31 The mailing list for DPDK development is `dev@dpdk.org <https://mails.dpdk.org/archives/dev/>`_.
78 T: git://dpdk.org/next/dpdk-next-crypto
133 git clone git://dpdk.org/dpdk
134 git clone https://dpdk.org/git/dpdk
138 git clone git://dpdk.org/next/dpdk-next-*
139 git clone https://dpdk.org/git/next/dpdk-next-*
324 should also be CCed to the `stable@dpdk.org <https://mails.dpdk.org/listinfo/stable>`_
333 Cc: stable@dpdk.org
442 ~/.config/dpdk/devel.config
443 /etc/dpdk/devel.config.
[all …]
/f-stack/dpdk/doc/guides/compressdevs/
H A Docteontx.rst70 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.1
71 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.2
72 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.3
73 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.4
74 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.5
75 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.6
76 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.7
77 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:01.0
/f-stack/dpdk/doc/guides/tools/
H A Ddevbind.rst4 dpdk-devbind Application
7 The ``dpdk-devbind`` tool is a Data Plane Development Kit (DPDK) utility
19 dpdk-devbind [options] DEVICE1 DEVICE2 ....
72 While any user can run the ``dpdk-devbind.py`` script to view the status of the network ports,
81 dpdk-devbind --status
85 dpdk-devbind --bind=vfio-pci eth1
89 dpdk-devbind -u 0000:01:00.0
93 dpdk-devbind -b ixgbe 02:00.0 02:00.1
98 dpdk-devbind --status
109 sudo dpdk-devbind -b vfio-pci 0000:0a:00.0
[all …]
H A Dhugepages.rst4 dpdk-hugepages Application
7 The ``dpdk-hugepages`` tool is a Data Plane Development Kit (DPDK) utility
19 dpdk-hugepages [options]
65 While any user can run the ``dpdk-hugpages.py`` script to view the
74 dpdk-hugpages.py -s
78 dpdk-hugpages.py -p 1G --setup 2G
H A Dpdump.rst6 dpdk-pdump Application
9 The ``dpdk-pdump`` tool is a Data Plane Development Kit (DPDK) tool that runs as
10 a DPDK secondary process and is capable of enabling packet capture on dpdk ports.
13 * The ``dpdk-pdump`` tool can only be used in conjunction with a primary
15 In dpdk, only the ``testpmd`` is modified to initialize packet capture
16 framework, other applications remain untouched. So, if the ``dpdk-pdump``
22 * The ``dpdk-pdump`` tool depends on DPDK pcap PMD, so the system should
26 * The ``dpdk-pdump`` tool runs as a DPDK secondary process. It exits when
37 ./<build_dir>/app/dpdk-pdump --
74 * As of now the ``dpdk-pdump`` tool cannot capture the packets of virtual devices
[all …]
H A Dpmdinfo.rst5 dpdk-pmdinfo Application
8 The ``dpdk-pmdinfo`` tool is a Data Plane Development Kit (DPDK) utility that
19 dpdk-pmdinfo [-hrtp] [-d <pci id file] <elf-file>
25 -p, --plugindir Scan dpdk for autoload plugins
H A Dproc_info.rst4 dpdk-procinfo Application
7 The dpdk-procinfo application is a Data Plane Development Kit (DPDK) application
20 ./<build_dir>/app/dpdk-procinfo -- -m | [-p PORTMASK] [--stats | --xstats |
75 * dpdk-procinfo should run alongside primary process with same DPDK version.
77 * When running ``dpdk-procinfo`` with shared library mode, it is required to
82 * Stats retrieval using ``dpdk-procinfo`` is not supported for virtual devices like PCAP and TAP.
84 * Since default DPDK EAL arguments for ``dpdk-procinfo`` are ``-c1, -n4 & --proc-type=secondary``,
/f-stack/dpdk/devtools/
H A Dload-devel-config7 test ! -r /etc/dpdk/devel.config ||
8 . /etc/dpdk/devel.config
10 test ! -r ~/.config/dpdk/devel.config ||
11 . ~/.config/dpdk/devel.config
/f-stack/
H A D.gitignore10 dpdk/x86_64-native-linuxapp-gcc/
11 dpdk/build/
29 dpdk/.ci/
30 dpdk/.travis.yml
/f-stack/dpdk/doc/guides/cryptodevs/
H A Docteontx.rst90 by using dpdk-devbind.py script. The OCTEON TX crypto PF device need to be
95 Once the required VFs are enabled, dpdk-devbind.py script can be used to
101 cd <dpdk directory>
102 ./usertools/dpdk-devbind.py -u <vf device no>
103 ./usertools/dpdk-devbind.py -b vfio-pci <vf device no>
130 ./dpdk-test
138 ./dpdk-test
H A Docteontx2.rst110 Another way to bind the VF would be to use the ``dpdk-devbind.py`` script:
114 cd <dpdk directory>
115 ./usertools/dpdk-devbind.py -u 0002:10:00.1
116 ./usertools/dpdk-devbind.py -b vfio-pci 0002:10.00.1
147 ./dpdk-test
155 ./dpdk-test
/f-stack/dpdk/doc/guides/sample_app_ug/
H A Dcompiling.rst16 cd dpdk/<build_dir>
33 Applications are output to: ``dpdk/<build_dir>/examples``.
47 cd dpdk/<build_dir>
69 applications are located in ``dpdk/examples/``.
/f-stack/doc/
H A DF-Stack_Quick_Start_Guide.md8 See Intel DPDK [linux_gsg](http://dpdk.org/doc/guides/linux_gsg/index.html)
19 cd /data/f-stack/dpdk
47 insmod /data/f-stack/dpdk/build/kernel/linux/igb_uio/igb_uio.ko
48 insmod /data/f-stack/dpdk/build/kernel/linux/kni/rte_kni.ko carrier=on
49 python dpdk-devbind.py --status
51 python dpdk-devbind.py --bind=igb_uio eth0 # assuming that use 10GE NIC and eth0
H A DF-Stack_Build_Guide.md15 # compile dpdk
16 $ cd /data/f-stack/dpdk
66 ## Compile dpdk in virtual machine
68 - f-stack/dpdk/kernel/linux/igb_uio/igb_uio.c line 274:
/f-stack/dpdk/app/test/
H A Dtest_trace_register.c9 RTE_TRACE_POINT_REGISTER(app_dpdk_test_tp, app.dpdk.test.tp)
10 RTE_TRACE_POINT_REGISTER(app_dpdk_test_fp, app.dpdk.test.fp)
/f-stack/dpdk/doc/guides/nics/
H A Dnull.rst17 ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 --vdev net_null0 --vdev net_null1 -- -i
29 ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 --vdev "net_null0,copy=1" -- -i
38 ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 --vdev "net_null0,size=256" -- -i

123456789