DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: Dex Chen <dex.chen@ruckuswireless.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] kni: allow per-net instances
Date: Tue, 27 Oct 2015 03:03:18 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A91DD03@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1445914597-16726-1-git-send-email-dex.chen@ruckuswireless.com>



> -----Original Message-----
> From: Dex Chen [mailto:dex.chen@ruckuswireless.com]
> Sent: Tuesday, October 27, 2015 10:57 AM
> To: dev@dpdk.org
> Cc: Zhang, Helin; Dex Chen
> Subject: [PATCH v3] kni: allow per-net instances
> 
> There is a global variable 'device_in_use' which is used to make sure only one
> instance is using /dev/kni device. If you were using LXC, you will find there is only
> one instance of KNI example could be run even different namespaces were
> created.
> 
> In order to have /dev/kni used simultaneously in different namespaces, making
> all of global variables as per network namespace variables.
> 
> With regard to single kernel thread mode, there will be one kernel thread for
> each of network namespace.
> 
> Signed-off-by: Dex Chen <dex.chen@ruckuswireless.com>
Acked-by: Helin Zhang <helin.zhang@intel.com>

And make sure checkpatch check has been done.

  reply	other threads:[~2015-10-27  3:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 10:12 [dpdk-dev] [PATCH] " Dex Chen
2015-10-21 15:40 ` Thomas Monjalon
2015-10-21 16:22 ` Stephen Hemminger
2015-10-22  3:28 ` Zhang, Helin
2015-10-26 10:41 ` [dpdk-dev] [PATCH v2] " Dex Chen
2015-10-27  2:56 ` [dpdk-dev] [PATCH v3] " Dex Chen
2015-10-27  3:03   ` Zhang, Helin [this message]
2015-11-04  1:29     ` Thomas Monjalon

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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A91DD03@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=dex.chen@ruckuswireless.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).