All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Mike Latimer <mlatimer@suse.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xl only waits 33 seconds for ballooning to complete
Date: Mon, 12 Jan 2015 17:29:25 +0000	[thread overview]
Message-ID: <54B40475.9050204@eu.citrix.com> (raw)
In-Reply-To: <2335831.uL1mkM9EnT@linux-4w67.dnsdhcp.provo.novell.com>

On 01/12/2015 05:04 PM, Mike Latimer wrote:
>> I'm inclined to say we could add an option to say "wait forever", or
>> to increase the period of the checks; but ultimately at some point
>> someone (either xl or the human) needs to timeout and say, "This is
>> never going to finish".  10s seems like a very conservative default.
> 
> Agreed. Is a better solution to increase the timeout to some larger number and 
> add an option to "wait forever"?

When I said "10s seems very conservative", I meant, "10s should be by
far long enough for something to happen".  If you can't free up at least
1k in 30s, then there is certainly something very unusual with your
system.  So I was recommending leaving that the default.

I'm not really sure under what conditions an admin might want to fiddle
with the timeout, however, so I'm having second thoughts about adding
new options.

 -George

  parent reply	other threads:[~2015-01-12 17:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 21:17 xl only waits 33 seconds for ballooning to complete Mike Latimer
2015-01-07  9:38 ` Ian Campbell
2015-01-08  1:11   ` Mike Latimer
2015-01-08 12:28     ` Ian Campbell
2015-01-12 12:36     ` George Dunlap
2015-01-12 17:04       ` Mike Latimer
2015-01-12 17:23         ` Ian Campbell
2015-01-12 17:29         ` George Dunlap [this message]
2015-01-12 17:55           ` Mike Latimer

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=54B40475.9050204@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=mlatimer@suse.com \
    --cc=xen-devel@lists.xen.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.