mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikita Danilov <nikita@clusterfs.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Con Kolivas <kernel@kolivas.org>,
	linux <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] add requeue task
Date: Tue, 2 Nov 2004 18:16:30 +0300	[thread overview]
Message-ID: <16775.42190.9404.303359@thebsh.namesys.com> (raw)
In-Reply-To: <41877F2D.6070200@yahoo.com.au>

Nick Piggin writes:
 > Con Kolivas wrote:
 > > add requeue task
 > > 
 > > 
 > > 
 > > ------------------------------------------------------------------------
 > > 
 > > We can requeue tasks for cheaper then doing a complete dequeue followed by
 > > an enqueue. Add the requeue_task function and perform it where possible.
 > > 
 > > Change the granularity code to requeue tasks at their best priority
 > > instead of changing priority while they're running. This keeps tasks at
 > > their top interactive level during their whole timeslice.
 > > 
 > 
 > I wonder... these things are all in sufficiently rarely used places,
 > that the icache miss might be more costly than the operations saved.
 > 
 > But....
 > 
 > > Signed-off-by: Con Kolivas <kernel@kolivas.org>
 > > 
 > > Index: linux-2.6.10-rc1-mm2/kernel/sched.c
 > > ===================================================================
 > > --- linux-2.6.10-rc1-mm2.orig/kernel/sched.c	2004-11-02 14:48:54.686316718 +1100
 > > +++ linux-2.6.10-rc1-mm2/kernel/sched.c	2004-11-02 14:52:51.805763544 +1100
 > > @@ -579,6 +579,16 @@ static void enqueue_task(struct task_str
 > >  }
 > >  
 > >  /*
 > > + * Put task to the end of the run list without the overhead of dequeue
 > > + * followed by enqueue.
 > > + */
 > > +static void requeue_task(struct task_struct *p, prio_array_t *array)
 > > +{
 > > +	list_del(&p->run_list);
 > > +	list_add_tail(&p->run_list, array->queue + p->prio);
 > > +}

Shouldn't this be

list_move_tail(&p->run_list, array->queue + p->prio);

?

Nikita.

  reply	other threads:[~2004-11-02 15:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02  4:07 Con Kolivas
2004-11-02 12:35 ` Nick Piggin
2004-11-02 15:16   ` Nikita Danilov [this message]
2004-11-02 22:07     ` Nick Piggin
2004-11-03  8:12     ` Con Kolivas
2004-11-02 12:42 ` Ingo Molnar
2004-11-02 12:52   ` Con Kolivas
2004-11-02 12:58     ` Ingo Molnar
2004-11-02 14:02       ` [PATCH] requeue at granularity intervals Con Kolivas
2004-11-02 14:00   ` [PATCH] add requeue task redo Con Kolivas

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=16775.42190.9404.303359@thebsh.namesys.com \
    --to=nikita@clusterfs.com \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    /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

all inboxes | Powered by JetHome®