kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, avi@redhat.com,
	mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH 1/2] rcu: export rcu_note_context_switch() function
Date: Mon, 2 May 2011 13:56:12 +0300	[thread overview]
Message-ID: <20110502105612.GJ18376@redhat.com> (raw)
In-Reply-To: <20110430125928.GJ2297@linux.vnet.ibm.com>

On Sat, Apr 30, 2011 at 05:59:28AM -0700, Paul E. McKenney wrote:
> On Fri, Apr 29, 2011 at 09:02:39PM +0300, Gleb Natapov wrote:
> > On Fri, Apr 29, 2011 at 01:39:04AM -0700, Paul E. McKenney wrote:
> > > On Fri, Apr 29, 2011 at 01:36:18AM -0700, Paul E. McKenney wrote:
> > > > On Thu, Apr 28, 2011 at 12:52:02PM +0300, Gleb Natapov wrote:
> > > > 
> > > > Hmmm....  This is interesting.  KVM being a module, we either expand
> > > > TINY_RCU's size a bit by making rcu_note_context_switch() be a real
> > > > function in rcutiny.c and adding an export, or we expand it by adding
> > > > two exports.
> > > > 
> > > > I would like to solve this without making TINY_RCU larger, and preferably
> > > > by making it smaller.  Any ideas come to mind?  (Other than making
> > > > KVM depend on CONFIG_SMP, which sounds too much like throwing out the
> > > > baby with the bathwater.)
> > > 
> > > Nothing quite like hitting "send" to make an idea show up...
> > > 
> > > In a UP kernel, does it actually help anything to have KVM
> > > tell RCU about executing in a guest?  If not, could we have a
> > > rcu_note_context_switch_kvm() that is a static inline empty function in
> > > TINY_RCU and maps to rcu_note_context_switch() for TREE_RCU?
> > > 
> > 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.
> 
> 							Thanx, Paul
> 
How significantly? As I wrote in other mail I compiled two TINY_RCU
kernel with and without the patch and I didn't see memory footprint
increase at all. May be I measure it incorrectly, but what I see is that
with out of line function + export text section becomes 64 byte bigger, but
data section becomes 64 byte smaller:

   text    data     bss     dec     hex filename
4544134  590596 2023424 7158154  6d398a vmlinux     inline
4544198  590532 2023424 7158154  6d398a vmlinux.ol  out of line

--
			Gleb.

  parent reply	other threads:[~2011-05-02 10:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28  9:52 [PATCH 0/2] make kvm guest mode to be rcu quiescent state Gleb Natapov
2011-04-28  9:52 ` [PATCH 1/2] rcu: export rcu_note_context_switch() function Gleb Natapov
2011-04-28 10:01   ` Avi Kivity
2011-04-28 10:11     ` Gleb Natapov
2011-04-29  8:36   ` Paul E. McKenney
2011-04-29  8:39     ` Paul E. McKenney
2011-04-29 18:02       ` Gleb Natapov
2011-04-29 18:23         ` Gleb Natapov
2011-04-30 12:59         ` Paul E. McKenney
2011-04-30 19:43           ` Avi Kivity
2011-05-02 10:56           ` Gleb Natapov [this message]
2011-05-02 13:36             ` Paul E. McKenney
2011-05-02 14:10               ` Gleb Natapov
2011-05-03  6:25                 ` Paul E. McKenney
2011-05-04 13:10                   ` Gleb Natapov
2011-04-28  9:52 ` [PATCH 2/2] KVM: make guest mode entry to be rcu quiescent state Gleb Natapov
2011-05-03 13:13   ` Marcelo Tosatti
2011-05-03 13:20     ` Avi Kivity
2011-05-03 13:21     ` Gleb Natapov
2011-05-03 13:29       ` Marcelo Tosatti
2011-05-03 13:39         ` Gleb Natapov
2011-05-03 15:42           ` Marcelo Tosatti

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=20110502105612.GJ18376@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).