From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Eric Dumazet <dada1@cosmosbay.com>,
dipankar@in.ibm.com, linux-input@vger.kernel.org,
dmitry.torokhov@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Question about usage of RCU in the input layer
Date: Sun, 22 Mar 2009 16:03:31 -0700 [thread overview]
Message-ID: <20090322230331.GM7148@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090322154433.1b2cb1b1@infradead.org>
On Sun, Mar 22, 2009 at 03:44:33PM -0700, Arjan van de Ven wrote:
> On Sun, 22 Mar 2009 13:52:12 -0700
> "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
>
> > On Sun, Mar 22, 2009 at 12:46:32PM -0700, Arjan van de Ven wrote:
> > > On Sun, 22 Mar 2009 09:53:24 -0700
> > > "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> > >
> > > > > > How many synchronize_rcu() calls are you seeing on the boot
> > > > > > path?
> > > > >
> > > > > I see 20 that hit the above code path (eg ones that wait) until
> > > > > userspace starts.
> > > >
> > > > So with well-behaved readers, the full sequence would be worth
> > > > something like 50-60 milliseconds.
> > >
> > > yeah it's about 10% if the total kernel boot time.. so it does
> > > start to matter
> >
> > Half-second boot, eh? That would indeed be impressive.
>
> half a second until calling init.. that's what I have today (with all
> drivers built in).. nothing really special needed for it
> (well a few small patches that are pending for 2.6.30 ;-)
I thought the measurement was until the desktop was running with no more
disk activity. ;-)
But in any case, I will see what I can do about speeding up
synchronize_rcu(). I will likely start with TREE_RCU, and I may need
some sort of indication that boot is in progress.
Thanx, Paul
next prev parent reply other threads:[~2009-03-22 23:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 4:58 Question about usage of RCU in the input layer Arjan van de Ven
2009-03-19 7:23 ` Dmitry Torokhov
2009-03-19 14:02 ` Arjan van de Ven
2009-03-19 8:56 ` Dipankar Sarma
2009-03-19 14:18 ` Arjan van de Ven
2009-03-20 2:07 ` Paul E. McKenney
2009-03-20 3:20 ` Arjan van de Ven
2009-03-20 4:45 ` Paul E. McKenney
2009-03-20 5:28 ` Eric Dumazet
2009-03-20 6:01 ` Dipankar Sarma
2009-03-20 6:35 ` Eric Dumazet
2009-03-20 13:50 ` Arjan van de Ven
2009-03-20 14:31 ` Paul E. McKenney
2009-03-20 18:13 ` Arjan van de Ven
2009-03-21 1:27 ` Paul E. McKenney
2009-03-21 4:58 ` Arjan van de Ven
2009-03-21 18:58 ` Paul E. McKenney
2009-03-21 19:51 ` Arjan van de Ven
2009-03-21 20:26 ` Eric Dumazet
2009-03-21 21:07 ` Paul E. McKenney
2009-03-22 3:40 ` Arjan van de Ven
2009-03-22 4:38 ` Paul E. McKenney
2009-03-22 4:51 ` Arjan van de Ven
2009-03-22 5:18 ` Paul E. McKenney
2009-03-22 5:53 ` Arjan van de Ven
2009-03-22 16:53 ` Paul E. McKenney
2009-03-22 19:46 ` Arjan van de Ven
2009-03-22 20:52 ` Paul E. McKenney
2009-03-22 22:44 ` Arjan van de Ven
2009-03-22 23:03 ` Paul E. McKenney [this message]
2009-03-22 23:16 ` Arjan van de Ven
2009-03-23 1:27 ` Paul E. McKenney
2009-04-03 1:27 ` Paul E. McKenney
2009-03-21 21:13 ` Arjan van de Ven
2009-03-20 22:21 ` Paul E. McKenney
2009-03-21 5:46 ` Dmitry Torokhov
2009-03-21 9:13 ` Eric Dumazet
2009-03-21 18:58 ` Paul E. McKenney
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=20090322230331.GM7148@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=arjan@infradead.org \
--cc=dada1@cosmosbay.com \
--cc=dipankar@in.ibm.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).