From: Andi Kleen <andi@firstfloor.org>
To: Dave Chinner <david@fromorbit.com>
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
Subject: Re: DNAME_INLINE_LEN versus CONFIG_GENERIC_LOCKBREAK
Date: Fri, 4 Jul 2014 05:16:33 +0200 [thread overview]
Message-ID: <20140704031633.GT5714@two.firstfloor.org> (raw)
In-Reply-To: <20140704013222.GH9508@dastard>
> 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.
prev parent reply other threads:[~2014-07-04 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 9:18 DNAME_INLINE_LEN versus CONFIG_GENERIC_LOCKBREAK Rasmus Villemoes
2014-07-03 19:53 ` Andi Kleen
2014-07-04 1:32 ` Dave Chinner
2014-07-04 3:16 ` Andi Kleen [this message]
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=20140704031633.GT5714@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=npiggin@kernel.dk \
--cc=viro@zeniv.linux.org.uk \
/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