From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andi Kleen <andi@firstfloor.org>
Subject: Re: DNAME_INLINE_LEN versus CONFIG_GENERIC_LOCKBREAK
Date: Fri, 4 Jul 2014 05:16:33 +0200
Message-ID: <20140704031633.GT5714@two.firstfloor.org>
References: <8761je94wk.fsf@rasmusvillemoes.dk>
 <87fviite1u.fsf@tassilo.jf.intel.com>
 <20140704013222.GH9508@dastard>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Andi Kleen <andi@firstfloor.org>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Nick Piggin <npiggin@kernel.dk>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
To: Dave Chinner <david@fromorbit.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <20140704013222.GH9508@dastard>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

> IF you've turned on debugging options, then you've already lost more
> performance that careful packing of the dentry slab cache gains you.
> There's no point in carefully tuning DNAME_INLINE_LEN for debug
> options - it's just code that will break and annoy people as debug
> implementations change.

lockbreak is not a debug option.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.