linux-kernel - Re: [PATCH 1/2] rcu: export rcu_note_context

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]

Message-ID: <4DBC6654.5030003@redhat.com>
Date:	Sat, 30 Apr 2011 22:43:16 +0300
From:	Avi Kivity <avi@...hat.com>
To:	paulmck@...ux.vnet.ibm.com
CC:	Gleb Natapov <gleb@...hat.com>, linux-kernel@...r.kernel.org,
	mtosatti@...hat.com, kvm@...r.kernel.org
Subject: Re: [PATCH 1/2] rcu: export rcu_note_context_switch() function

On 04/30/2011 03:59 PM, Paul E. McKenney wrote:
> >  That will work, but does making rcu_note_context_switch() out of line
> >  actually increase kernel size? The function is called in two places
> >  currently, so by making it out of line we make two calling site smaller.
> >  Will measure it next week.
>
> One thing to keep in mind...  Calling an out-of-line function from
> KVM requires an export, each of which significantly increases TINY_RCU's
> memory footprint.

I would expect that most kvm configs will actually be smp (perhaps with 
an exception for embedded ppc).

A completely random idea - how about trimming exports that aren't 
actually used?  so if you have a minimal setup you only get the hit if 
you actually use kvm.

(The trimming would need to be optional so external modules can continue 
to work for those who want them)


-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

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