public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Bruce Rogers <brogers@novell.com>
Cc: stable@kernel.org, avi@redhat.com, kvm@vger.kernel.org
Subject: Re: [stable] [PATCH 3/3][STABLE] KVM: add schedule check to napi_enable	 call
Date: Thu, 3 Jun 2010 15:51:57 -0700	[thread overview]
Message-ID: <20100603225157.GB6986@kroah.com> (raw)
In-Reply-To: <4C07D59E02000048000974F1@sinclair.provo.novell.com>

On Thu, Jun 03, 2010 at 04:17:34PM -0600, Bruce Rogers wrote:
>  >>> On 6/3/2010 at 03:03 PM, Greg KH <greg@kroah.com> wrote: 
> > On Thu, Jun 03, 2010 at 01:38:31PM -0600, Bruce Rogers wrote:
> >>     virtio_net: Add schedule check to napi_enable call
> >>     Under harsh testing conditions, including low memory, the guest would
> >>     stop receiving packets. With this patch applied we no longer see any
> >>     problems in the driver while performing these tests for extended periods
> >>     of time.
> >> 
> >>     Make sure napi is scheduled subsequent to each napi_enable.
> >> 
> >>     Signed-off-by: Bruce Rogers <brogers@novell.com>
> >>     Signed-off-by: Olaf Kirch <okir@suse.de>
> > 
> > I need a git commit id for this one as well.
> > 
> 
> This one is not upstream.

Then I can't include it in the -stable tree, so why are you sending it
to me?  :)

thanks,

greg k-h

  reply	other threads:[~2010-06-03 22:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 19:38 [PATCH 3/3][STABLE] KVM: add schedule check to napi_enable call Bruce Rogers
2010-06-03 21:03 ` [stable] " Greg KH
2010-06-03 22:17   ` Bruce Rogers
2010-06-03 22:51     ` Greg KH [this message]
2010-06-04  0:02       ` Bruce Rogers
2010-06-04  0:02       ` Bruce Rogers
2010-12-03 15:44         ` Peter Lieven
2010-12-06 16:12           ` Avi Kivity

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=20100603225157.GB6986@kroah.com \
    --to=greg@kroah.com \
    --cc=avi@redhat.com \
    --cc=brogers@novell.com \
    --cc=kvm@vger.kernel.org \
    --cc=stable@kernel.org \
    /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