linux-kernel - Re: [PATCHSET sched/core] sched: prepare for cmwq

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sun, 23 May 2010 11:05:44 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Tejun Heo <tj@...nel.org>
Cc:	peterz@...radead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCHSET sched/core] sched: prepare for cmwq


* Tejun Heo <tj@...nel.org> wrote:

> Hello, Peter, Ingo.
> 
> On 05/18/2010 01:13 AM, Tejun Heo wrote:
> > On 05/13/2010 12:48 PM, Tejun Heo wrote:
> >> These four patches are the scheduler modifications necessary for cmwq
> >> and contains the following four patches.
> > 
> > Ping.
> > 
> 
> I know we're inside -rc1 merge window but I'm really 
> hoping to push cmwq through linux-next during this devel 
> cycle as the whole thing basically has been blocked 
> unchanged on scheduler changes for a couple of months 
> now.  So, can we please get this thing moving?

IIRC these changes are for some sort of speedup for btrfs, 
right?

I would really like to see before/after numbers on some 
important FS workload. How much of a speedup does it give?

Thanks,

	Ingo
--
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/