mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "quan.xu04@gmail.com" <quan.xu04@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	kvm <kvm@vger.kernel.org>, Quan Xu <quan.xu0@gmail.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH RFC v3 4/6] Documentation: Add three sysctls for smart idle poll
Date: Wed, 15 Nov 2017 09:16:56 +0100	[thread overview]
Message-ID: <20171115081656.at4cllb53pprfbtz@gmail.com> (raw)
In-Reply-To: <b44f8fad-55ee-ff03-faf9-d8ef4b8f4ab8@gmail.com>


* quan.xu04@gmail.com <quan.xu04@gmail.com> wrote:

> > > could I only leave paravirt_poll_threshold_ns parameter (the maximum poll time),
> > > which is as similar as "adaptive halt-polling" Wanpeng mentioned.. then user can
> > > turn it off, or find an appropriate threshold for some odd scenario..
> > That way lies utter madness. Maybe add it as a debugfs knob, but exposing it to
> > userspace: NAK.
> > 
> .. so, I will make these 3 parameters by default in next v4.
>      paravirt_poll_threshold_ns = 200000
>      paravirt_poll_shrink = 2
>      paravirt_poll_grow = 2
> 
> neither touch the syscal ABI nor expose it to userspace again.

Note that you can still expose it to developers via debugfs knobs.

I.e. same development and testing flexibility, but no ABI promise and an implicit 
expectation for this mechanism to be self-tuning.

Thanks,

	Ingo

      reply	other threads:[~2017-11-15  8:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1510570064-6178-1-git-send-email-quan.xu0@gmail.com>
2017-11-13 15:08 ` Ingo Molnar
2017-11-14  4:05   ` Quan Xu
2017-11-14  7:44     ` Ingo Molnar
2017-11-15  3:15       ` quan.xu04
2017-11-15  8:16         ` Ingo Molnar [this message]

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=20171115081656.at4cllb53pprfbtz@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quan.xu04@gmail.com \
    --cc=quan.xu0@gmail.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
Powered by JetHome