From: David Miller <davem@davemloft.net>
To: jean-louis@dupond.be
Cc: netdev@vger.kernel.org, Paul.Durrant@citrix.com,
wei.liu2@citrix.com, xen-devel@lists.xenproject.org
Subject: Re: [PATCH net] xen-netback: correctly schedule rate-limited queues
Date: Thu, 27 Jul 2017 09:35:44 -0700 (PDT) [thread overview]
Message-ID: <20170727.093544.904406679221141579.davem__30512.8910266378$1501173423$gmane$org@davemloft.net> (raw)
In-Reply-To: <ba4a971ce2c0891a6e911ef09b6a5d6e@dupond.be>
From: Jean-Louis Dupond <jean-louis@dupond.be>
Date: Thu, 27 Jul 2017 10:21:56 +0200
> Op 2017-06-22 17:16, schreef David Miller:
>> From: Wei Liu <wei.liu2@citrix.com>
>> Date: Wed, 21 Jun 2017 10:21:22 +0100
>>
>>> Add a flag to indicate if a queue is rate-limited. Test the flag in
>>> NAPI poll handler and avoid rescheduling the queue if true, otherwise
>>> we risk locking up the host. The rescheduling will be done in the
>>> timer callback function.
>>> Reported-by: Jean-Louis Dupond <jean-louis@dupond.be>
>>> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
>>> Tested-by: Jean-Louis Dupond <jean-louis@dupond.be>
>> Applied.
>
> Could this get applied to stable & LTS kernels also?
> Seems important enough in my opinion.
Sure, queued up.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-27 16:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 9:21 [PATCH net] xen-netback: correctly schedule rate-limited queues Wei Liu
2017-06-21 9:38 ` Paul Durrant
2017-06-21 9:38 ` Paul Durrant
2017-06-22 15:16 ` David Miller
2017-07-27 8:21 ` Jean-Louis Dupond
2017-07-27 8:21 ` Jean-Louis Dupond
2017-07-27 16:35 ` David Miller
2017-07-27 16:35 ` David Miller [this message]
2017-06-22 15:16 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2017-06-21 9:21 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='20170727.093544.904406679221141579.davem__30512.8910266378$1501173423$gmane$org@davemloft.net' \
--to=davem@davemloft.net \
--cc=Paul.Durrant@citrix.com \
--cc=jean-louis@dupond.be \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 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.