From: Jiri Slaby <jslaby@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>, Greg KH <greg@kroah.com>
Cc: Josef Bacik <jbacik@fb.com>, stable <stable@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>, Chris Mason <clm@fb.com>
Subject: Re: Name hashing function causing a perf regression
Date: Mon, 15 Sep 2014 18:53:00 +0200 [thread overview]
Message-ID: <5417196C.2050100@suse.cz> (raw)
In-Reply-To: <CA+55aFy0LVzxWUasLkJ391bnMMmgfwgCv=9ZrrbW1u9mVQL9Yg@mail.gmail.com>
On 09/15/2014, 06:45 PM, Linus Torvalds wrote:
> On Mon, Sep 15, 2014 at 9:35 AM, Greg KH <greg@kroah.com> wrote:
>>
>> Thanks, now queued up. Note, I had to change the 3.10-stable patch a
>> bit due to some rejects.
>
> Ahh. Yes. it still uses the old D_HASHBITS/HASHMASK macros in up until
> and including 3.12.
>
> You could have just backported 482db9066199 ("dcache.c: get rid of
> pointless macros") too
Ok, I went this path for 3.12 as 482db9066199 is simple enough. Thanks!
--
js
suse labs
next prev parent reply other threads:[~2014-09-15 16:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 19:30 Name hashing function causing a perf regression Josef Bacik
2014-09-12 19:11 ` Andi Kleen
2014-09-12 19:21 ` Linus Torvalds
2014-09-12 19:52 ` Josef Bacik
2014-09-12 20:39 ` Linus Torvalds
2014-09-12 21:25 ` Josef Bacik
2014-09-12 22:01 ` Linus Torvalds
2014-09-12 22:08 ` Josef Bacik
2014-09-12 22:25 ` Linus Torvalds
2014-09-13 18:58 ` Linus Torvalds
2014-09-15 1:32 ` Linus Torvalds
2014-09-15 2:49 ` Tetsuo Handa
2014-09-15 3:37 ` Linus Torvalds
2014-09-15 4:58 ` Tetsuo Handa
2014-09-15 14:17 ` Linus Torvalds
2014-09-15 15:55 ` Josef Bacik
2014-09-15 16:22 ` Linus Torvalds
2014-09-15 16:25 ` Al Viro
2014-09-15 16:33 ` Linus Torvalds
2014-09-15 16:35 ` Greg KH
2014-09-15 16:45 ` Linus Torvalds
2014-09-15 16:53 ` Jiri Slaby [this message]
2014-09-15 17:31 ` Greg KH
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=5417196C.2050100@suse.cz \
--to=jslaby@suse.cz \
--cc=andi@firstfloor.org \
--cc=clm@fb.com \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=jbacik@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.