From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Emelyanov Subject: Re: [PATCH 1/5] Add notification about some major slab events Date: Thu, 27 Sep 2007 12:25:26 +0400 Message-ID: <46FB68F6.6000902@openvz.org> References: <46F91841.9070708@openvz.org> <46F91898.5060400@openvz.org> <46FA285B.5060709@openvz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Christoph Lameter Cc: Linux Containers , Balbir Singh List-Id: containers.vger.kernel.org Christoph Lameter wrote: > On Wed, 26 Sep 2007, Pavel Emelyanov wrote: > >> True, but we mark the slubs as notifyable at runtime, after they >> are merged. However, once someone decides to make his slab notifyable >> from the very beginning this makes sense, thanks. > > This also makes sense if a device driver later creates a new slab. Adding > the bit will switch off additional merges for that slab. True. I will fix it. Thanks. >> Oh, great! Does this mean I can put Acked-by when sending this to Andrew? > > Yes. Great! Thanks a lot! Pavel