public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Cc: Vitaly Mayatskikh <vmayatsk@redhat.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH 2.6.21] Return available first timeslice to the creator, not parent
Date: Thu, 30 Aug 2007 11:14:59 +0200	[thread overview]
Message-ID: <1188465299.6112.34.camel@twins> (raw)
In-Reply-To: <46D681B4.90401@stud.feec.vutbr.cz>

On Thu, 2007-08-30 at 10:37 +0200, Michal Schmidt wrote:
> Vitaly Mayatskikh skrev:
> > Short-living process returns its timeslice to the parent, this
> > affects process that creates a lot of such short-living threads,
> > because its not a parent for new threads.
> 
> I don't see the point of sending patches for old Linux versions such as 
> 2.6.21, unless it's something applicable to the -stable tree.

The older trees might want to have this, perhaps the .16 by Adrian,
certainly distros still care.

> Do recent kernels with CFS have the same problem?

Very much not comparable, as you probably guessed :-)

> > Patch fixes this issue and
> > doesn't break kabi as does the patch from reporter:
> > http://lkml.org/lkml/2007/4/7/21
> 
> There's no kabi.

True.


  reply	other threads:[~2007-08-30  9:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30  7:50 [PATCH 2.6.21] Return available first timeslice to the creator, not parent Vitaly Mayatskikh
2007-08-30  8:37 ` Michal Schmidt
2007-08-30  9:14   ` Peter Zijlstra [this message]
2007-08-30  9:10 ` Peter Zijlstra
2007-08-30  9:48   ` Pavel Emelyanov
2007-08-30  9:49   ` Oleg Nesterov
2007-08-30  9:56     ` Peter Zijlstra
2007-08-30 10:09       ` Oleg Nesterov

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=1188465299.6112.34.camel@twins \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=vmayatsk@redhat.com \
    --cc=xschmi00@stud.feec.vutbr.cz \
    /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