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 v5] windows/netuio: add Windows NetUIO kernel driver
Date: Mon, 5 Oct 2020 12:34:04 -0700 [thread overview]
Message-ID: <20201005193404.GA4932@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <7f5f4978-f967-66e8-5152-5446198bfd42@intel.com>
On Fri, Oct 02, 2020 at 11:21:54AM -0700, Ranjit Menon wrote:
>
> On 10/1/2020 3:55 PM, Narcisa Ana Maria Vasile wrote:
> >From: Narcisa Vasile <navasile@microsoft.com>
> >
> >The Windows netuio kernel driver provides the DPDK userspace application
> >with direct access to hardware, by mapping the HW registers in userspace
> >and allowing read/write operations from/to the device
> >configuration space.
> >
> >Two IOCTLs are defined by the netuio interface:
> > * IOCTL_NETUIO_MAP_HW_INTO_USERSPACE
> > - used for mapping the device registers into userspace
> > * IOCTL_NETUIO_PCI_CONFIG_IO
> > - used to read/write from/into the device configuration space
> >
> >Note:
> >Requests to map the device BARs into userspace need to be processed
> >in the thread context of the process that initiated the mapping request.
> >Otherwise, the BARs might end up mapped into an arbitrary process
> >address space.
> >EvtIoInCallerContext is used to ensure the requests are handled
> >in the right user thread context. Other requests (PCI config)
> >are sent back to the framework and processed by the EvtIoDeviceControl
> >callback.
> >
> >Cc: Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>
> >Cc: Omar Cardona <ocardona@microsoft.com>
> >Cc: Dmitry Malloy <dmitrym@microsoft.com>
> >Signed-off-by: Narcisa Vasile <navasile@microsoft.com>
> >---
> >
>
> We'll need to do a code-style cleanup at some point, but for now:
>
Yes, agreed. I'll send a patch for style cleanup after merging this one.
Thanks, Ranjit.
> Reviewed-by: Ranjit Menon <ranjit.menon@intel.com>
>
> Acked-by: Ranjit Menon <ranjit.menon@intel.com>
next prev parent reply other threads:[~2020-10-05 19:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 22:23 [dpdk-dev] [PATCH v2] " Narcisa Ana Maria Vasile
2020-08-21 1:32 ` Ranjit Menon
2020-09-09 18:58 ` Narcisa Ana Maria Vasile
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 [this message]
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=20201005193404.GA4932@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).