public inbox for linux-api@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Khalid Aziz <khalid.aziz@oracle.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	corbet@lwn.net, mingo@redhat.com, hpa@zytor.com, riel@redhat.com,
	akpm@linux-foundation.org, rientjes@google.com,
	ak@linux.intel.com, mgorman@suse.de, raistlin@linux.it,
	kirill.shutemov@linux.intel.com, atomlin@redhat.com,
	avagin@openvz.org, gorcunov@openvz.org,
	serge.hallyn@canonical.com, athorlton@sgi.com, oleg@redhat.com,
	vdavydov@parallels.com, daeseok.youn@gmail.com,
	keescook@chromium.org, yangds.fnst@cn.fujitsu.com,
	sbauer@eng.utah.edu, vishnu.ps@samsung.com, axboe@fb.com,
	paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH RESEND v4] sched/fair: Add advisory flag for borrowing a timeslice
Date: Fri, 19 Dec 2014 00:02:29 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1412182355020.17382@nanos> (raw)
In-Reply-To: <54935842.5020507@oracle.com>

On Thu, 18 Dec 2014, Khalid Aziz wrote:
> On 12/18/2014 03:28 PM, Peter Zijlstra wrote:
> > On Thu, Dec 18, 2014 at 11:44:19AM -0700, Khalid Aziz wrote:
> > > sched/fair: Add advisory flag for borrowing a timeslice
> > 
> > yuck hatred and much of that.
> > 
> > Also, you fail to explain why a kernel side spin futex-lock is not an
> > option.
> > 
> 
> I had explained that when this question came up in the last round of
> discussions. The queuing problem I am trying to solve stems from userspace
> locks. Java and databases implement their own userspace locks that do not use
> futex. Solving this with futex will not help the primary users of this
> solution.

If we can solve it with a proper designed and well thought out
functionality in the kernel based on a futex like mechanism, why cant
java and databases not switch over to that and simply use it?

You need to modify user space anyway, so it does not matter whether
you modify it in a sane or in a hacky way.

But its simpler to hack crap into the scheduler than coming up with a
proper solution to the problem, right?

> Hope this helps.

Not at all.

Thanks,

	tglx

  reply	other threads:[~2014-12-18 23:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 18:44 [PATCH RESEND v4] sched/fair: Add advisory flag for borrowing a timeslice Khalid Aziz
2014-12-18 22:28 ` Peter Zijlstra
2014-12-18 22:42   ` Khalid Aziz
2014-12-18 23:02     ` Thomas Gleixner [this message]
2014-12-18 23:38       ` Khalid Aziz
2014-12-19  0:27         ` Thomas Gleixner
2014-12-19 21:43           ` Khalid Aziz
2014-12-19 23:57             ` Thomas Gleixner
2014-12-22 16:40               ` Khalid Aziz
     [not found]                 ` <5498498B.90703-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2014-12-23 10:52                   ` Ingo Molnar
2014-12-23 15:13                     ` Khalid Aziz
2014-12-23 18:46                       ` Rik van Riel
2014-12-23 20:47                         ` Khalid Aziz
     [not found]                           ` <5499D4D7.90109-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2014-12-23 22:33                             ` Rik van Riel
2015-01-13 11:25                         ` Peter Zijlstra

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=alpine.DEB.2.11.1412182355020.17382@nanos \
    --to=tglx@linutronix.de \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=athorlton@sgi.com \
    --cc=atomlin@redhat.com \
    --cc=avagin@openvz.org \
    --cc=axboe@fb.com \
    --cc=corbet@lwn.net \
    --cc=daeseok.youn@gmail.com \
    --cc=gorcunov@openvz.org \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=khalid.aziz@oracle.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=raistlin@linux.it \
    --cc=riel@redhat.com \
    --cc=rientjes@google.com \
    --cc=sbauer@eng.utah.edu \
    --cc=serge.hallyn@canonical.com \
    --cc=vdavydov@parallels.com \
    --cc=vishnu.ps@samsung.com \
    --cc=yangds.fnst@cn.fujitsu.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