* [dpdk-dev] [vmxnet3 PATCH] doc: describe kernel dependency and --vmware-tsc-map
@ 2013-07-25 20:38 Thomas Monjalon
2013-07-26 9:01 ` Damien Millescamps
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Monjalon @ 2013-07-25 20:38 UTC (permalink / raw)
To: dev
Be more verbose on kernel dependency about version and parameters.
And add description of DPDK parameter for VMware.
Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
README.rst | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/README.rst b/README.rst
index 55436a4..c718ec7 100644
--- a/README.rst
+++ b/README.rst
@@ -49,6 +49,9 @@ HOW TO BUILD
There are two build dependencies: Linux kernel headers and DPDK >= 1.2.3r3.
+The kernel driver is based on vmxnet3-8.6.10 from VMware ESXi-5.0.0u2.
+So the latest supported Linux version is 3.2.
+
DPDK must be built first in order to have all its header files in the same
directory, that RTE_INCLUDE must point to.
@@ -93,15 +96,19 @@ Other parameters have a global effect:
- ``num_rxds=int``: number of RX descriptors per queue
- ``num_txds=int``: number of TX descriptors per queue
+Because the kernel module initializes interfaces, **it's very important that
+DPDK parameters match kernel ones**. It won't work otherwise.
+
For more information, use ``modinfo vmxnet3-usermap.ko``.
-The values of the kernel module parameters must match the DPDK ones.
+In userland, librte_pmd_vmxnet3.so must be loaded by the DPDK using the ``-d``
+option.
-Because the kernel module initializes interfaces, it's very important that
-DPDK parameters match kernel ones. It won't work otherwise.
+Another interesting option is ``--vmware-tsc-map``.
+It allows VMware TSC mapping which provides an access to physical TSC.
+When this option is used, take care of setting this ESXi parameter::
-In userland, librte_pmd_vmxnet3.so must be loaded by the DPDK using the "-d"
-option.
+ monitor_control.pseudo_perfctr = TRUE
``testpmd`` example for two ports, matching the ``insmod`` command above::
--
1.7.10.4
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] [vmxnet3 PATCH] doc: describe kernel dependency and --vmware-tsc-map
2013-07-25 20:38 [dpdk-dev] [vmxnet3 PATCH] doc: describe kernel dependency and --vmware-tsc-map Thomas Monjalon
@ 2013-07-26 9:01 ` Damien Millescamps
2013-07-26 9:07 ` Thomas Monjalon
0 siblings, 1 reply; 3+ messages in thread
From: Damien Millescamps @ 2013-07-26 9:01 UTC (permalink / raw)
To: dev
On 07/25/2013 10:38 PM, Thomas Monjalon wrote:
> Be more verbose on kernel dependency about version and parameters.
> And add description of DPDK parameter for VMware.
>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> ---
> README.rst | 17 ++++++++++++-----
> 1 file changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/README.rst b/README.rst
> index 55436a4..c718ec7 100644
> --- a/README.rst
> +++ b/README.rst
> @@ -49,6 +49,9 @@ HOW TO BUILD
>
> There are two build dependencies: Linux kernel headers and DPDK >= 1.2.3r3.
>
> +The kernel driver is based on vmxnet3-8.6.10 from VMware ESXi-5.0.0u2.
> +So the latest supported Linux version is 3.2.
> +
> DPDK must be built first in order to have all its header files in the same
> directory, that RTE_INCLUDE must point to.
>
> @@ -93,15 +96,19 @@ Other parameters have a global effect:
> - ``num_rxds=int``: number of RX descriptors per queue
> - ``num_txds=int``: number of TX descriptors per queue
>
> +Because the kernel module initializes interfaces, **it's very important that
> +DPDK parameters match kernel ones**. It won't work otherwise.
> +
> For more information, use ``modinfo vmxnet3-usermap.ko``.
>
> -The values of the kernel module parameters must match the DPDK ones.
> +In userland, librte_pmd_vmxnet3.so must be loaded by the DPDK using the ``-d``
> +option.
>
> -Because the kernel module initializes interfaces, it's very important that
> -DPDK parameters match kernel ones. It won't work otherwise.
> +Another interesting option is ``--vmware-tsc-map``.
> +It allows VMware TSC mapping which provides an access to physical TSC.
> +When this option is used, take care of setting this ESXi parameter::
>
> -In userland, librte_pmd_vmxnet3.so must be loaded by the DPDK using the "-d"
> -option.
> + monitor_control.pseudo_perfctr = TRUE
>
> ``testpmd`` example for two ports, matching the ``insmod`` command above::
>
ack
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] [vmxnet3 PATCH] doc: describe kernel dependency and --vmware-tsc-map
2013-07-26 9:01 ` Damien Millescamps
@ 2013-07-26 9:07 ` Thomas Monjalon
0 siblings, 0 replies; 3+ messages in thread
From: Thomas Monjalon @ 2013-07-26 9:07 UTC (permalink / raw)
To: Damien Millescamps; +Cc: dev
26/07/2013 11:01, Damien Millescamps :
> On 07/25/2013 10:38 PM, Thomas Monjalon wrote:
> > Be more verbose on kernel dependency about version and parameters.
> > And add description of DPDK parameter for VMware.
>
> ack
pushed
--
Thomas
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-07-26 9:07 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-07-25 20:38 [dpdk-dev] [vmxnet3 PATCH] doc: describe kernel dependency and --vmware-tsc-map Thomas Monjalon
2013-07-26 9:01 ` Damien Millescamps
2013-07-26 9:07 ` Thomas Monjalon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).