From: David Vrabel <david.vrabel@citrix.com>
To: Zoltan Kiss <zoltan.kiss@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Cc: <netdev@vger.kernel.org>, <xen-devel@lists.xenproject.org>,
David Vrabel <david.vrabel@citrix.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen-netback: Turn off the carrier if the guest is not able to receive
Date: Mon, 4 Aug 2014 14:35:32 +0100 [thread overview]
Message-ID: <53DF8C24.6030709@citrix.com> (raw)
In-Reply-To: <1406749849-4356-2-git-send-email-zoltan.kiss@citrix.com>
On 30/07/14 20:50, Zoltan Kiss wrote:
> Currently when the guest is not able to receive more packets, qdisc layer starts
> a timer, and when it goes off, qdisc is started again to deliver a packet again.
> This is a very slow way to drain the queues, consumes unnecessary resources and
> slows down other guests shutdown.
> This patch change the behaviour by turning the carrier off when that timer
> fires, so all the packets are freed up which were stucked waiting for that vif.
> Instead of the rx_queue_purge bool it uses the VIF_STATUS_RX_PURGE_EVENT bit to
> signal the thread that either the timout happened or an RX interrupt arrived, so
> the thread can check what it should do. It also disables NAPI, so the guest
> can't transmit, but leaves the interrupts on, so it can resurrect.
I don't think you should disable NAPI, particularly since you have to
fiddle with the bits directly instead of usign the API to do so.
I looked at some hardware drivers and none of them disabled NAPI -- they
just allow it to naturally end once hardware queues are drained.
netback is a little different as a frontend could stop processing
to-guest packets but continue sending from-guest ones. I don't see any
problem with allowing this.
> @@ -1955,24 +1955,78 @@ int xenvif_kthread_guest_rx(void *data)
> */
> if (unlikely(queue->vif->disabled && queue->id == 0))
> xenvif_carrier_off(queue->vif);
> + else if (unlikely(test_and_clear_bit(QUEUE_STATUS_RX_PURGE_EVENT,
> + &queue->status))) {
> + /* Either the last unsuccesful skb or at least 1 slot
> + * should fit
> + */
> + int needed = queue->rx_last_skb_slots ?
> + queue->rx_last_skb_slots : 1;
>
> - if (kthread_should_stop())
> - break;
> -
> - if (queue->rx_queue_purge) {
> + /* It is assumed that if the guest post new
> + * slots after this, the RX interrupt will set
> + * the bit and wake up the thread again
> + */
> + set_bit(QUEUE_STATUS_RX_STALLED, &queue->status);
This big if needs to go in a new function.
David
next prev parent reply other threads:[~2014-08-04 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 19:50 [PATCH] xen-netback: Using a new state bit instead of carrier Zoltan Kiss
2014-07-30 19:50 ` [PATCH] xen-netback: Turn off the carrier if the guest is not able to receive Zoltan Kiss
2014-08-01 4:53 ` David Miller
2014-08-01 10:52 ` Wei Liu
2014-08-04 15:04 ` Zoltan Kiss
2014-08-04 13:35 ` David Vrabel [this message]
2014-08-04 15:13 ` [Xen-devel] " Zoltan Kiss
2014-08-08 16:33 ` Stephen Hemminger
2014-08-11 12:31 ` Zoltan Kiss
2014-08-11 12:37 ` David Vrabel
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=53DF8C24.6030709@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 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).