All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Durrant <paul.durrant@citrix.com>
To: "Xu, Dongxiao" <dongxiao.xu@intel.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH] VNIF: Using smart polling instead of event notification.
Date: Thu, 1 Oct 2009 15:21:10 +0100	[thread overview]
Message-ID: <4AC4BAD6.8070804@citrix.com> (raw)
In-Reply-To: <EADF0A36011179459010BDF5142A457501CEB99EAF@pdsmsx502.ccr.corp.intel.com>

Xu, Dongxiao wrote:
>     We found that the event notification frequency is still high in some network cases. NAPI polls only for a little
> time slot and does not efficient enough in our backend/frontend case. Actually our patch repeated calling NAPI
> interface to do more polling, and netback will NOT notify netfront during this period. Once netfront polling out
> all the data, and finds that there is no more data arrive/send during the next 100ms, the timer will stop working 
> to end the polling. 
>     This filed 'smart_poll_active' is shared by netfront and netback, to indicate whether netfront is polling data. 
> So this filed is necessary for netback to notify netfront if this flag is not set. 
> This field is different from the flag in xenstore, which indicates whether other-end has this new feature. If other-end doesn't support the new feature, everything goes in the original way. 
> 

If you want to prevent event notification, why not simply mask out your 
port?

   Paul

  reply	other threads:[~2009-10-01 14:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01 14:02 [PATCH] VNIF: Using smart polling instead of event notification Xu, Dongxiao
2009-10-01 14:21 ` Paul Durrant [this message]
2009-10-02  9:41 ` Ian Campbell
2009-10-02 19:10   ` Jeremy Fitzhardinge
  -- strict thread matches above, loose matches on Subject: below --
2009-10-01  0:22 Xu, Dongxiao
2009-10-01 10:03 ` Ian Campbell
2009-09-30 18:17 Xu, Dongxiao

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=4AC4BAD6.8070804@citrix.com \
    --to=paul.durrant@citrix.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=dongxiao.xu@intel.com \
    --cc=xen-devel@lists.xensource.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.