2021-10-09 12:38 (UTC-0700), Kadam, Pallavi:
> On 10/8/2021 2:11 PM, Dmitry Kozlyuk wrote:
> > [...]
> > +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

This link is given above and I consider it general information for all
drivers. However, reading it carefully, I think docs in dpdk-kmods could be
restructured as well:
* Keep windows/README.rst unchanged, except for Device Manager steps,
  which are actually specific to virt2phys.
* Create windows/virt2phys/README.rst with instructions above.
* Change windows/netuio/README.rst: remove the bulk of its content, as it
  repeats generic instructions, keep netuio-specific Device Manager part.
Then a specific link for virt2phys here would make sense
and there will be even less duplication in dpdk-kmods.
If no one objects, I'll do this in v2.
Thanks!

Reply via email to