DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Vamsi Attunuru <vattunuru@marvell.com>, dpdk-dev <dev@dpdk.org>,
	 Thomas Monjalon <thomas@monjalon.net>,
	Jerin Jacob <jerinj@marvell.com>,
	techboard@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1 1/1] kernel/linux: introduce vfio_pf kernel module
Date: Thu, 24 Oct 2019 16:38:46 +0530	[thread overview]
Message-ID: <CALBAE1Ni7oJO_PjwS9xb8OdzCQKm6rLo0UBMXCK5SAFa5EewYQ@mail.gmail.com> (raw)
In-Reply-To: <20191009162831.0c1cf204@hermes.lan>

> > >
> >
> > There is security issue in attaching DPDK PF driver and netdev bind to VF.
> > So this scheme is not upsteamble to Linux kernel. Since rte_flow had VF
> > action. We need this scheme to support VF action with VFIO. So, Out of tree
> > is the only way as it is DPDK specific feature. Already sent patches to
> > Linux kernel, it make sense to not accept this in upstream.  We are already
> > exposing such features through igb-uio for non VFIO device. IMO, there
> > should not be any disparity between igb-uio and VFIO in DPDK.
> >
> > If we are against out of tree module, let's remove igb-uio as well. We
> > can't have different treatment for similar issues.
>
> You are right igb-uio is legacy and only exists for users unwilling to
> change (such as old kernels which don't support vfio noiommu mode).
> Eventually it should go as well. And the same for KNI.

+ Techboard

I understand, Everyone would like not to have out of tree kernel
modules in dpdk repo.

Is it possible to
a) move existing or new out of tree module or
b) libraries can be used by another project or
c) DPDK device drivers binary FW repo like Linux kernel FW etc(The
ones connected to dpdk)

add it in https://www.dpdk.org/hosted-projects/

and use tools like "https://gerrit.googlesource.com/git-repo/"[1] for
development and distribution case
[1]
git-repo: tools used by android for a similar situation.

      parent reply	other threads:[~2019-10-24 11:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06  9:12 vattunuru
2019-09-06  9:45 ` Thomas Monjalon
2019-09-06 13:27   ` Jerin Jacob Kollanukkaran
2019-09-25  4:06     ` Vamsi Krishna Attunuru
2019-09-25  7:18       ` Andrew Rybchenko
2019-10-08  5:07     ` Vamsi Krishna Attunuru
2019-10-31 17:03     ` Thomas Monjalon
2019-11-01 11:54       ` Luca Boccassi
2019-11-01 12:12         ` Jerin Jacob
2019-11-04 11:16         ` Bruce Richardson
2019-11-05 10:09           ` Luca Boccassi
2019-11-06 22:32       ` Alex Williamson
2019-11-07  5:02         ` Jerin Jacob
2019-11-15  6:57           ` Thomas Monjalon
2019-11-15  7:01             ` Jerin Jacob
2019-10-08 15:12 ` Stephen Hemminger
2019-10-08 15:28   ` Jerin Jacob
2019-10-09 23:28     ` Stephen Hemminger
2019-10-10  6:02       ` Jerin Jacob
2019-10-13  7:20         ` Jerin Jacob
2019-10-16 11:37           ` Jerin Jacob
2019-10-23 17:08             ` Jerin Jacob
2019-10-24 11:08       ` Jerin Jacob [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=CALBAE1Ni7oJO_PjwS9xb8OdzCQKm6rLo0UBMXCK5SAFa5EewYQ@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=stephen@networkplumber.org \
    --cc=techboard@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=vattunuru@marvell.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).