From: Matthew Wilcox <willy@infradead.org>
To: "zhengbin (A)" <zhengbin13@huawei.com>
Cc: Hugh Dickins <hughd@google.com>,
viro@zeniv.linux.org.uk, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, houtao1@huawei.com,
yi.zhang@huawei.com, "J. R. Okajima" <hooanon05g@gmail.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH] tmpfs: use ida to get inode number
Date: Fri, 22 Nov 2019 18:33:25 -0800 [thread overview]
Message-ID: <20191123023325.GY20752@bombadil.infradead.org> (raw)
In-Reply-To: <77f67d7a-4a93-4319-e6af-54daffcc37e2@huawei.com>
On Sat, Nov 23, 2019 at 10:16:39AM +0800, zhengbin (A) wrote:
> By the way, percpu IDA is for reducing performance impact? This patch has 2.16%
> performance degradation(Use perf to get the cost of ida_alloc_range)
2.16% degradation in your tests ... I bet Eric didn't make it so complex
for only 2% performance impact. Unfortunately, he didn't give any
numbers in his patch submission, but it's going to be a bigger problem
on multi-socket machines than on a laptop.
Eric, any memories from 2010? Commit
f991bd2e14210fb93d722cb23e54991de20e8a3d if it helps.
next prev parent reply other threads:[~2019-11-23 2:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 14:23 [PATCH] tmpfs: use ida to get inode number zhengbin
2019-11-20 15:45 ` Matthew Wilcox
2019-11-21 2:36 ` zhengbin (A)
2019-11-21 4:52 ` Hugh Dickins
2019-11-21 6:45 ` zhengbin (A)
2019-11-21 19:53 ` Hugh Dickins
2019-11-22 1:23 ` zhengbin (A)
2019-11-22 22:13 ` Matthew Wilcox
2019-11-23 2:16 ` zhengbin (A)
2019-11-23 2:33 ` Matthew Wilcox [this message]
2019-11-23 4:54 ` Al Viro
2019-12-01 8:44 ` zhengbin (A)
2019-11-21 11:40 ` J. R. Okajima
2019-11-21 20:07 ` Hugh Dickins
2019-11-21 4:31 ` Al Viro
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=20191123023325.GY20752@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=eric.dumazet@gmail.com \
--cc=hooanon05g@gmail.com \
--cc=houtao1@huawei.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yi.zhang@huawei.com \
--cc=zhengbin13@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).