From: Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>
To: Ranjit Menon <ranjit.menon@intel.com>
Cc: dev@dpdk.org, thomas@monjalon.net, ocardona@microsoft.com,
haramakr@linux.microsoft.com, pallavi.kadam@intel.com,
dmitry.kozliuk@gmail.com, dmitrym@microsoft.com,
Narcisa Vasile <navasile@microsoft.com>,
Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH v2] windows/netuio: add Windows NetUIO kernel driver
Date: Wed, 9 Sep 2020 11:58:36 -0700 [thread overview]
Message-ID: <20200909185836.GB13245@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <c0c8dd7c-e1fb-5c35-0436-23a3452a28fa@intel.com>
On Thu, Aug 20, 2020 at 06:32:02PM -0700, Ranjit Menon wrote:
> Hi, Naty
>
> On 8/20/2020 3:23 PM, Narcisa Ana Maria Vasile wrote:
> >From: Narcisa Vasile <navasile@microsoft.com>
> >
> >The Windows NetUIO kernel driver allows the DPDK userspace
> >application to directly access the hardware.
> >
> >Cc: Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>
> >Cc: Omar Cardona <ocardona@microsoft.com>
> >Signed-off-by: Narcisa Vasile <navasile@microsoft.com>
> >---
> >
> I haven't reviewed the code yet, but a few general suggestions and
> observations:
>
> 1. This code is going into the dpdk-kmods repo, so we don't need the
> four-level deep directory path for the source.
>
> 2. The code can simply be in the windows/netuio directory (don't
> need 'kernel')
>
> 3. The 'virt2phys' module that is already in the repo puts the
> build-related files (project files, solution files etc) in the same
> folder as the source files. We should do the same here. We don't
> need the mk/exec-env subfolder for these files. They can be in the
> same directory as the source.
>
> 4. Remove the .vcxproj.user file from the patch. It is not required.
>
> 5. The README should be renamed to simply README.rst and it can also
> be in this windows/netuio folder
>
> 6. The existing README.rst in the windows folder contains
> information on how to build and load kernel modules in Windows. This
> new README can reference the root-level README, if required. (Also
> some of the information in this new README is out-of-date. I'll
> review that separately)
>
>
> ranjit m.
>
Thank you, Ranjit! I've cleaned it up and sent v3.
next prev parent reply other threads:[~2020-09-09 18:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 22:23 Narcisa Ana Maria Vasile
2020-08-21 1:32 ` Ranjit Menon
2020-09-09 18:58 ` Narcisa Ana Maria Vasile [this message]
2020-08-24 20:53 ` Dmitry Kozlyuk
2020-09-09 18:53 ` Narcisa Ana Maria Vasile
2020-09-13 21:39 ` Dmitry Kozlyuk
2020-09-09 18:41 ` [dpdk-dev] [PATCH v3] " Narcisa Ana Maria Vasile
2020-09-13 21:39 ` Dmitry Kozlyuk
2020-09-19 2:52 ` [dpdk-dev] [PATCH v4] " Narcisa Ana Maria Vasile
2020-09-22 21:25 ` Dmitry Kozlyuk
2020-09-22 21:36 ` Ranjit Menon
2020-10-01 22:55 ` [dpdk-dev] [PATCH v5] " Narcisa Ana Maria Vasile
2020-10-02 18:21 ` Ranjit Menon
2020-10-05 19:34 ` Narcisa Ana Maria Vasile
2020-10-14 9:29 ` Thomas Monjalon
2020-10-02 18:33 ` Dmitry Kozlyuk
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=20200909185836.GB13245@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=navasile@linux.microsoft.com \
--cc=Harini.Ramakrishnan@microsoft.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=haramakr@linux.microsoft.com \
--cc=navasile@microsoft.com \
--cc=ocardona@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=thomas@monjalon.net \
/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).