All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Wei Liu <wei.liu2@citrix.com>,
	netdev@vger.kernel.org, xen-devel@lists.xen.org
Cc: Ian Campbell <ian.campbell@citrix.com>,
	Zoltan Kiss <zoltan.kiss@citrix.com>
Subject: Re: [PATCH net v2 1/3] xen-netback: move NAPI add/remove calls
Date: Fri, 08 Aug 2014 20:49:10 +0400	[thread overview]
Message-ID: <53E4FF86.8040505@cogentembedded.com> (raw)
In-Reply-To: <1407515833-2550-2-git-send-email-wei.liu2@citrix.com>

Hello.

On 08/08/2014 08:37 PM, Wei Liu wrote:

> Originally napi_add was in init_queue and napi_del was in deinit_queue,
> while kthreads were handled in _connect and _disconnect. Move napi_add
> and napi_remove

    netif_napi_{add|del}()?

 > to _connect and _disconnect so that they reside togother

    Together.

> with kthread operations.

> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> Cc: Ian Campbell <ian.campbell@citrix.com>
> Cc: Zoltan Kiss <zoltan.kiss@citrix.com>

WBR, Sergei

  parent reply	other threads:[~2014-08-08 16:49 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08 16:37 [PATCH net v2 0/3] xen-netback: synchronisation between core driver and netback Wei Liu
2014-08-08 16:37 ` [PATCH net v2 1/3] xen-netback: move NAPI add/remove calls Wei Liu
2014-08-08 16:49   ` Sergei Shtylyov
2014-08-08 16:49   ` Sergei Shtylyov [this message]
2014-08-08 16:52     ` Wei Liu
2014-08-08 16:52     ` Wei Liu
2014-08-11 12:35   ` David Vrabel
2014-08-11 12:35   ` [Xen-devel] " David Vrabel
2014-08-11 12:49     ` Zoltan Kiss
2014-08-11 12:49     ` [Xen-devel] " Zoltan Kiss
2014-08-11 13:01       ` David Vrabel
2014-08-11 13:01       ` [Xen-devel] " David Vrabel
2014-08-11 13:14         ` Zoltan Kiss
2014-08-11 13:43           ` Wei Liu
2014-08-11 13:43           ` [Xen-devel] " Wei Liu
2014-08-11 13:59             ` David Vrabel
2014-08-11 14:08               ` Wei Liu
2014-08-11 14:08               ` [Xen-devel] " Wei Liu
2014-08-11 13:59             ` David Vrabel
2014-08-11 13:14         ` Zoltan Kiss
2014-08-08 16:37 ` Wei Liu
2014-08-08 16:37 ` [PATCH net v2 2/3] xen-netback: don't stop dealloc kthread too early Wei Liu
2014-08-08 16:37 ` Wei Liu
2014-08-11 12:10   ` David Vrabel
2014-08-11 12:10   ` [Xen-devel] " David Vrabel
2014-08-11 13:48     ` Wei Liu
2014-08-11 13:48     ` [Xen-devel] " Wei Liu
2014-08-11 13:58       ` David Vrabel
2014-08-11 13:58       ` [Xen-devel] " David Vrabel
2014-08-11 14:13         ` Zoltan Kiss
2014-08-11 14:44           ` Wei Liu
2014-08-11 15:23             ` David Vrabel
2014-08-11 20:39               ` Wei Liu
2014-08-11 20:39               ` [Xen-devel] " Wei Liu
2014-08-11 15:23             ` David Vrabel
2014-08-11 14:44           ` Wei Liu
2014-08-11 14:13         ` Zoltan Kiss
2014-08-11 14:31         ` Wei Liu
2014-08-11 14:31         ` [Xen-devel] " Wei Liu
2014-08-11 14:34           ` David Vrabel
2014-08-11 14:39             ` Wei Liu
2014-08-11 14:39             ` [Xen-devel] " Wei Liu
2014-08-11 14:34           ` David Vrabel
2014-08-08 16:37 ` [PATCH net v2 3/3] xen-netback: remove loop waiting function Wei Liu
2014-08-08 16:37 ` Wei Liu

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=53E4FF86.8040505@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=ian.campbell@citrix.com \
    --cc=netdev@vger.kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=zoltan.kiss@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.