linux-kernel - Re: [PATCH v2] sched: Accelerate "pick_next

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, 29 Jan 2012 17:33:28 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Michael Wang <wangyun@...ux.vnet.ibm.com>
Cc:	Cong Wang <xiyou.wangcong@...il.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Xiaotian Feng <xtfeng@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] sched: Accelerate "pick_next_entity" under special
 condition


* Michael Wang <wangyun@...ux.vnet.ibm.com> wrote:

> On 01/27/2012 12:42 PM, Cong Wang wrote:
> 
> > On 01/27/2012 09:22 AM, Michael Wang wrote:
> >> Hi, Ingo
> >>
> >> Thanks for your reply.
> >>
> >> I have try use "ls -l" to see the size of sched.o, but after applied the
> >> patch, it is still 1636.
> >>
> >> I have not use this method before, may be I use the wrong command...
> >>
> >> But I think the new code should be similar to the old one after compile,
> >> because we still have 3 condition check here.
> >>
> >> I suppose the new sched.o will be a little bigger, because one jump
> >> command and a label need to be added.
> >>
> > 
> > Try to see if `size` helps.
> 
> Hi, Cong
> 
> Thanks for your advise, but still, the size not changed.
> 
> And also I don't know whether the size can be some kind of 
> proof to confirm the performance improvement in this case...

You could disassemble the .o file via objdump -d and run diff on 
it - is there any change in the code generated by GCC?

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/