linux-kernel - Re: [PATCH] Give kjournald a IOPRIO_CLASS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081002210117.0f5062f7@infradead.org>
Date:	Thu, 2 Oct 2008 21:01:17 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Jens Axboe <jens.axboe@...cle.com>, linux-kernel@...r.kernel.org,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH] Give kjournald a IOPRIO_CLASS_RT io priority

On Thu, 2 Oct 2008 13:24:57 -0700
Andrew Morton <akpm@...ux-foundation.org> wrote:

> Of course, that could all be wrong and we could be stuck somewhere
> else.  A good way to diagnose this stuff would be
> 
> --- a/kernel/sched.c~a
> +++ a/kernel/sched.c
> @@ -5567,10 +5567,14 @@ EXPORT_SYMBOL(yield);
>  void __sched io_schedule(void)
>  {
>  	struct rq *rq = &__raw_get_cpu_var(runqueues);
> +	unsigned long in, out;
>  
>  	delayacct_blkio_start();
>  	atomic_inc(&rq->nr_iowait);
> +	in = jiffies;
>  	schedule();
> +	out = jiffies;
> +	WARN_ON(time_after(out, in + 1 * HZ));
>  	atomic_dec(&rq->nr_iowait);
>  	delayacct_blkio_end();
>  }
> _
> 
> perhaps for varying values of "1".

I'll run with this. (well with a value of "1000" for 1 ;-)

Also I'll tell latencytop to give me the full backtrace as well ;-)


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/