From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Thenveer Poolakkanni <thenveer.poolakkanni@iwave-global.com>,
Thomas Monjalon <thomas@monjalon.net>,
"andremue@linux.microsoft.com" <andremue@linux.microsoft.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Chaturbhuja Nath Prabhu <c.prabhu@iwave-global.com>,
Ayshathul Thuhara <ayshathul.thuhara@iwave-global.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: Assistance with DPDK on Windows
Date: Mon, 1 Dec 2025 12:20:51 +0300 [thread overview]
Message-ID: <49bc7ad0-89fa-4b47-9720-94e5c54cf72a@gmail.com> (raw)
In-Reply-To: <PN3P287MB0273EF115C985B4AF616B13EB7DBA@PN3P287MB0273.INDP287.PROD.OUTLOOK.COM>
Hi Thenveer,
virt2phys does not conflict with netuio, because virt2phys does not bind
to any NIC.
It is just loaded into the kernel for DPDK to make IOCTLs to get
physical addresses.
There are specific instruction for loading virt2phys:
https://git.dpdk.org/dpdk-kmods/tree/windows/README.rst
On 12/1/25 12:13, Thenveer Poolakkanni wrote:
> Hi Team,
> Additionally, I have one more query: how do I use the
> *virt2phys* driver when I have two network interfaces already bound to
> *netuio*?
> Thanks,
> Thenveer
prev parent reply other threads:[~2025-12-01 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PN3P287MB0273982789E89005206DA9B0B7C4A@PN3P287MB0273.INDP287.PROD.OUTLOOK.COM>
[not found] ` <85f9def5-7f88-47d1-9dc8-524b060c54e5@gmail.com>
[not found] ` <2455856.MHSsGVy7CF@thomas>
2025-11-14 10:12 ` Thenveer Poolakkanni
2025-12-01 5:55 ` Thenveer Poolakkanni
2025-12-01 9:13 ` Thenveer Poolakkanni
2025-12-01 9:20 ` Dmitry Kozlyuk [this message]
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=49bc7ad0-89fa-4b47-9720-94e5c54cf72a@gmail.com \
--to=dmitry.kozliuk@gmail.com \
--cc=andremue@linux.microsoft.com \
--cc=ayshathul.thuhara@iwave-global.com \
--cc=c.prabhu@iwave-global.com \
--cc=dev@dpdk.org \
--cc=thenveer.poolakkanni@iwave-global.com \
--cc=thomas@monjalon.net \
--cc=users@dpdk.org \
/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).