DPDK patches and discussions
 help / color / mirror / Atom feed
From: William Tu <u9012063@gmail.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC PATCH 5/5] mk/windows: add virtio-net PMD
Date: Sun, 15 Aug 2021 07:28:18 -0700	[thread overview]
Message-ID: <CALDO+Sajk6dG067BGrOz6SSrYNJ86FJo74TvmXK_MZH7c_zPxg@mail.gmail.com> (raw)
In-Reply-To: <20210814200057.35207d86@sovereign>

On Sat, Aug 14, 2021 at 10:01 AM Dmitry Kozlyuk
<dmitry.kozliuk@gmail.com> wrote:
>
> 2021-08-14 08:55 (UTC-0700), William Tu:
> > Hi Dmitry,
> >
> > I'm looking at this patch and have some questions.
> >
> > On Thu, Feb 27, 2020 at 10:08 PM Dmitry Kozlyuk
> > <dmitry.kozliuk@gmail.com> wrote:
> > >
> > > Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
> > > ---
> > >  drivers/net/virtio/virtio_ethdev.c            |   4 +
> > >  kernel/windows/netuio/netuio.inf              |   6 +
> > >  lib/librte_eal/windows/eal/eal.c              |   4 +
> >
> > Why do we need these change below?
>
> 1. At the time of the patch there was no dpdk-kmods repo.
>
> 2. The patch is for dpdk-draft-windows repo,
>    which was using Vistual Studio projects instead of meson.
>
> > I thought to add a new Windows driver support, we only need to
> > compile the drivers/net/xxx, and add the device ID to netuio.inf,
> > at the dpdk-kmod repo?
>
> Yes.
> Particularly for virtio it would also be required to support reading PCI
> config space in bus/pci/windows (netuio already provides the support).
>
Now I understand, thanks. William

      reply	other threads:[~2021-08-15 14:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-08  8:45 [dpdk-dev] Windows Draft Build Dmitry Kozlyuk
2020-02-10  5:03 ` Ranjit Menon
2020-02-10  6:14   ` Dmitry Kozlyuk
2020-02-17  1:14     ` Dmitry Kozlyuk
2020-02-18 21:44       ` Ranjit Menon
2020-02-25  2:37         ` Dmitry Kozlyuk
2020-02-25  9:06           ` Ranjit Menon
2020-02-26  6:22             ` Dmitry Kozlyuk
2020-02-27  4:11               ` Dmitry Kozlyuk
2020-02-27 15:25                 ` William Tu
2020-02-27 15:42                   ` David Marchand
2020-02-28  6:07                 ` [dpdk-dev] [RFC PATCH 0/5] virtio-net support for Windows draft Dmitry Kozlyuk
2020-02-28  6:07                   ` [dpdk-dev] [RFC PATCH 1/5] pci/windows: add stubs for port IO Dmitry Kozlyuk
2020-02-28  6:07                   ` [dpdk-dev] [RFC PATCH 2/5] net: add stub for RARP packet generation on Windows Dmitry Kozlyuk
2020-02-28  6:07                   ` [dpdk-dev] [RFC PATCH 3/5] pci/windows: split config I/O into series of fixed-size operations Dmitry Kozlyuk
2020-02-28  6:07                   ` [dpdk-dev] [RFC PATCH 4/5] netuio: change class for Net to custom Dmitry Kozlyuk
2020-02-28  6:07                   ` [dpdk-dev] [RFC PATCH 5/5] mk/windows: add virtio-net PMD Dmitry Kozlyuk
2021-08-14 15:55                     ` William Tu
2021-08-14 17:00                       ` Dmitry Kozlyuk
2021-08-15 14:28                         ` William Tu [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=CALDO+Sajk6dG067BGrOz6SSrYNJ86FJo74TvmXK_MZH7c_zPxg@mail.gmail.com \
    --to=u9012063@gmail.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@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).