DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kadam, Pallavi" <pallavi.kadam@intel.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>, <dev@dpdk.org>
Cc: William Tu <u9012063@gmail.com>,
	Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
	Dmitry Malloy <dmitrym@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH] doc/windows_gsg: update section on driver installation
Date: Sat, 9 Oct 2021 12:38:07 -0700	[thread overview]
Message-ID: <7d8f6e0f-5a5a-54c8-22aa-151493dcd316@intel.com> (raw)
In-Reply-To: <20211008211154.349793-1-dmitry.kozliuk@gmail.com>


On 10/8/2021 2:11 PM, Dmitry Kozlyuk wrote:
> Windows GSG included a section only on virt2phys driver installation,
> but not on NetUIO. The content of the section duplicated documentation
> in dpdk-kmods, but contained no links to it, only a reference.
>
> Add subsections for virt2phys and NetUIO, explaining their roles.
> Refer to documenttion in dpdk-kmods as an authoritative source,
> but leave specific diagnostic and usage hints in the GSG.
>
> Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
> ---
>   doc/guides/windows_gsg/run_apps.rst | 48 ++++++++++++++---------------
>   1 file changed, 23 insertions(+), 25 deletions(-)
>
> diff --git a/doc/guides/windows_gsg/run_apps.rst b/doc/guides/windows_gsg/run_apps.rst
> index abaecc3793..70bb1da33f 100644
> --- a/doc/guides/windows_gsg/run_apps.rst
> +++ b/doc/guides/windows_gsg/run_apps.rst
> @@ -27,40 +27,27 @@ See `Large-Page Support`_ in MSDN for details.
>   .. _Large-Page Support: https://docs.microsoft.com/en-us/windows/win32/memory/large-page-support
>   
>   
> -Load virt2phys Driver
> ----------------------
> +Install Drivers
> +---------------
>   
> -Access to physical addresses is provided by a kernel-mode driver, virt2phys.
> -It is mandatory at least for using hardware PMDs, but may also be required
> -for mempools.
> -
> -Refer to documentation in ``dpdk-kmods`` repository for details on system
> -setup, driver build and installation. This driver is not signed, so signature
> -checking must be disabled to load it.
> +Certain kernel-mode drivers are required to run DPDK applications.
> +Refer to `Windows documentation <https://git.dpdk.org/dpdk-kmods/tree/windows>`_
> +in ``dpdk-kmods`` repository for common instructions on system setup,
> +driver build and installation. The drivers are not signed, so signature
> +enforcement has to be disabled.
>   
>   .. warning::
>   
>       Disabling driver signature enforcement weakens OS security.
>       It is discouraged in production environments.
>   
> -Compiled package consists of ``virt2phys.inf``, ``virt2phys.cat``,
> -and ``virt2phys.sys``. It can be installed as follows
> -from Elevated Command Prompt:
> -
> -.. code-block:: console
> -
> -    pnputil /add-driver Z:\path\to\virt2phys.inf /install
>   
> -On Windows Server additional steps are required:
> +virt2phys
> +~~~~~~~~~
>   
> -1. From Device Manager, Action menu, select "Add legacy hardware".
> -2. It will launch the "Add Hardware Wizard". Click "Next".
> -3. Select second option "Install the hardware that I manually select
> -   from a list (Advanced)".
> -4. On the next screen, "Kernel bypass" will be shown as a device class.
> -5. Select it, and click "Next".
> -6. The previously installed drivers will now be installed for the
> -   "Virtual to physical address translator" device.
> +Access to physical addresses is provided by a kernel-mode driver, virt2phys.
> +It is mandatory for allocating physically-contiguous memory which is required
> +by hardware PMDs.

Should we add specific link to virt2phys README in this section as well?

https://git.dpdk.org/dpdk-kmods/tree/windows/README.rst

>   
>   When loaded successfully, the driver is shown in *Device Manager* as *Virtual
>   to physical address translator* device under *Kernel bypass* category.
> @@ -74,6 +61,17 @@ on initialization (debug-level logs provide more details):
>       EAL: Cannot open virt2phys driver interface
>   
>   
> +NetUIO
> +~~~~~~
> +
> +NetUIO kernel-mode driver provides access to the device hardware resources.
> +It is mandatory for all hardware PMDs, except for MLX5 PMD.
> +
> +Refer to `NetUIO documentation <https://git.dpdk.org/dpdk-kmods/tree/windows/netuio/README.rst>`_
> +in ``dpdk-kmods`` repository for instructions to build and set up the driver.
> +Devices supported by NetUIO are listed in ``netuio.inf``.
> +The list can be extended in order to try running DPDK with new devices.
> +
>   
>   Run the ``helloworld`` Example
>   ------------------------------

  reply	other threads:[~2021-10-09 19:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 21:11 Dmitry Kozlyuk
2021-10-09 19:38 ` Kadam, Pallavi [this message]
2021-10-09 20:20   ` Dmitry Kozlyuk
2021-10-10  1:28     ` William Tu
2021-10-11 16:33     ` Kadam, Pallavi
2021-10-11 19:15 ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7d8f6e0f-5a5a-54c8-22aa-151493dcd316@intel.com \
    --to=pallavi.kadam@intel.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=dmitrym@microsoft.com \
    --cc=navasile@linux.microsoft.com \
    --cc=u9012063@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).