[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150623003119.GF3892@linux.vnet.ibm.com>
Date: Mon, 22 Jun 2015 17:31:19 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Dave Hansen <dave@...1.net>, Andi Kleen <ak@...ux.intel.com>,
dave.hansen@...ux.intel.com, akpm@...ux-foundation.org,
jack@...e.cz, viro@...iv.linux.org.uk, eparis@...hat.com,
john@...nmccutchan.com, rlove@...ve.org,
tim.c.chen@...ux.intel.com, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] fs: optimize inotify/fsnotify code for unwatched
files
On Mon, Jun 22, 2015 at 09:03:08PM +0200, Peter Zijlstra wrote:
> On Mon, Jun 22, 2015 at 09:29:49AM -0700, Paul E. McKenney wrote:
>
> > I believe that there still are some cases. But why would offline
> > CPUs seem so iffy? CPUs coming up execute code before they are fully
> > operational, and during that time, much of the kernel views them as
> > being offline. Yet they do have to execute significant code in order
> > to get themselves set up.
>
> I'm thinking we do far too much during bringup and tear-down as it is.
> But yes maybe.
Boot, suspend, and hibernation indeed would be faster if we did less,
but we still will have to do something.
Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists