DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Amin Saba <amn.brhm.sb@gmail.com>
Cc: dev@dpdk.org, parasjha13@gmail.com,
	Thomas Monjalon <thomas@monjalon.net>,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] KNI for FreeBSD.
Date: Tue, 14 May 2019 12:35:00 +0100	[thread overview]
Message-ID: <d36b2224-1dab-61c8-6333-d36c697dd506@intel.com> (raw)
Message-ID: <20190514113500.YpPKqoVeEn-xnsZXDVQ28BUgDt90hu67d-RZsWszfnM@z> (raw)
In-Reply-To: <CAMuas+eH3pn6YxNtK3XAcr=PqLcA1YAv8iVU0F0nGAztq8sf0A@mail.gmail.com>

On 5/14/2019 11:27 AM, Amin Saba wrote:
> Hi all,
> 
> Are there any specific issues in FreeBSD that have prevented implementation
> of KNI?
> 
> Is implementation of KNI for FreeBSD in your roadmap?

It is not in the roadmap as far as I know.

cc'ed Paras, if I remember correctly he also mentioned from this support in the
past, perhaps there can be some collaboration.

The issue I can think of as a blocker is a new kernel module code in the DPDK
repo, previously guidance was to upstream kernel related code into kernel source.
cc'ed Thomas & Stephen.

  parent reply	other threads:[~2019-05-14 11:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 10:27 Amin Saba
2019-05-14 10:27 ` Amin Saba
2019-05-14 11:21 ` Burakov, Anatoly
2019-05-14 11:21   ` Burakov, Anatoly
2019-05-14 11:35 ` Ferruh Yigit [this message]
2019-05-14 11:35   ` Ferruh Yigit
2019-05-14 12:37 ` Ray Kinsella
2019-05-14 12:37   ` Ray Kinsella
2019-05-14 12:42   ` Bruce Richardson
2019-05-14 12:42     ` Bruce Richardson

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=d36b2224-1dab-61c8-6333-d36c697dd506@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=amn.brhm.sb@gmail.com \
    --cc=dev@dpdk.org \
    --cc=parasjha13@gmail.com \
    --cc=stephen@networkplumber.org \
    --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).