public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] add requeue task
Date: Tue, 02 Nov 2004 23:35:57 +1100	[thread overview]
Message-ID: <41877F2D.6070200@yahoo.com.au> (raw)
In-Reply-To: <418707E5.90705@kolivas.org>

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);
> +}
> +
> +/*
>   * Used by the migration code - we pull tasks from the head of the
>   * remote queue so we want these tasks to show up at the head of the
>   * local queue:
> @@ -2425,8 +2435,7 @@ void scheduler_tick(void)
>  			set_tsk_need_resched(p);
>  
>  			/* put it at the end of the queue: */
> -			dequeue_task(p, rq->active);
> -			enqueue_task(p, rq->active);
> +			requeue_task(p, rq->active);
>  		}
>  		goto out_unlock;
>  	}
> @@ -2467,10 +2476,8 @@ void scheduler_tick(void)
>  			(p->time_slice >= TIMESLICE_GRANULARITY(p)) &&
>  			(p->array == rq->active)) {
>  
> -			dequeue_task(p, rq->active);
> +			requeue_task(p, rq->active);
>  			set_tsk_need_resched(p);
> -			p->prio = effective_prio(p);
> -			enqueue_task(p, rq->active);
>  		}
>  	}
>  out_unlock:

This isn't a 1:1 transformation. Looks like the effective_prio there
might be superfluous, but if so that should be a different patch.

> @@ -3569,8 +3576,14 @@ asmlinkage long sys_sched_yield(void)
>  	} else if (!rq->expired->nr_active)
>  		schedstat_inc(rq, yld_exp_empty);
>  
> -	dequeue_task(current, array);
> -	enqueue_task(current, target);
> +	if (array != target) {
> +		dequeue_task(current, array);
> +		enqueue_task(current, target);
> +	} else
> +		/*
> +		 * requeue_task is cheaper so perform that if possible.
> +		 */
> +		requeue_task(current, array);
>  
>  	/*
>  	 * Since we are going to call schedule() anyway, there's
> 

Hmm if you have to go to this trouble I'd say its not worth it.
Ingo may want to weigh in though.

  reply	other threads:[~2004-11-02 13:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02  4:07 [PATCH] add requeue task Con Kolivas
2004-11-02 12:35 ` Nick Piggin [this message]
2004-11-02 15:16   ` Nikita Danilov
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=41877F2D.6070200@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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