DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>,
	Omar Cardona <ocardona@microsoft.com>,
	Dmitry Malloy <dmitrym@microsoft.com>,
	Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
	Pallavi Kadam <pallavi.kadam@intel.com>,
	Ranjit Menon <ranjit.menon@intel.com>,
	Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
	Tal Shnaiderman <talshn@mellanox.com>,
	Fady Bader <fady@mellanox.com>, Ophir Munk <ophirmu@mellanox.com>
Subject: [dpdk-dev] Fwd: [Minutes 04/15/2020] Bi-Weekly DPDK Windows Community Call
Date: Wed, 15 Apr 2020 23:02:44 +0200	[thread overview]
Message-ID: <4064679.AiC22s8V5E@thomas> (raw)

From: Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>

Attendees: Thomas Monjalon, Ranjit Menon, Tal Shnaiderman, Pallavi Kadam, Ranjit Menon, Narcisa Ana Maria Vasile, Harini Ramakrishnan, Dmitry Kozliuk, William Tu, Tasnim Bashar


1/ UIO Driver

  *   New Intel-Microsoft DA needed to unblock licensing issues.
  *   Naty will apply fixes with Dmitry K's feedback on UIO source.
  *   After licensing headers on source files are updated, release process for build and binary to begin.
  *   [AI Harini & Ranjit] To expedite licensing agreement resolution to unblock UIO driver release.


2/ Dmitry's Patches on EAL's memory management interface, virt2phys driver

  *   Naty and Ranjit have reviewed EAL and virt2phys driver
  *   Dmitry sent v3 patches with review comments.
  *   Vitr2phys driver code integrated in kmods repo
  *   Awaiting memory management community maintainer review, Dmitry M's comments on patches
  *   Awaiting comments on impact on Linux and FreeBSD code
  *   Awaiting Dmitry M's comment on patches.
  *   [AI Dmitry K, Harini] Dmitry K to send summary of conversation for feedback, Harini to follow-up for resolution.
  *   [AI Dmitry K] To send out v4 after all reviews are addressed.


3/ PCI Probing

  *   Mellanox internally reviewing patches for PCI bus
  *   Will be send out for review in the next 2 weeks.
  *   Next step is for Intel to provides patches for specific steps needed when probing PCI devices which are bound to netuio.


4/ Opens

  *   Intel is working to get logging patch set, will be sent out for review in few weeks.
  *   [AI Harini] Need Microsoft expert allocation to drive issues for clang compiler support for Windows DPDK

        *   https://bugs.llvm.org/show_bug.cgi?id=24383
        *   Harini to setup a focused conversation around prioritization of DPDK for Windows.
     *   IHVs not acknowledging Roadmap proposal will be removed from Roadmap.




             reply	other threads:[~2020-04-15 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 21:02 Thomas Monjalon [this message]
2020-04-16 23:46 ` [dpdk-dev] " Dmitry Kozlyuk
2020-04-17  7:47   ` Thomas Monjalon
2020-04-17 15:10     ` 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=4064679.AiC22s8V5E@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=dmitrym@microsoft.com \
    --cc=fady@mellanox.com \
    --cc=harini.ramakrishnan@microsoft.com \
    --cc=navasile@linux.microsoft.com \
    --cc=ocardona@microsoft.com \
    --cc=ophirmu@mellanox.com \
    --cc=pallavi.kadam@intel.com \
    --cc=ranjit.menon@intel.com \
    --cc=talshn@mellanox.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).