From: Chris Down <chris@chrisdown.name>
To: "zhengbin (A)" <zhengbin13@huawei.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Matthew Wilcox <willy@infradead.org>,
Jeff Layton <jlayton@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>, Tejun Heo <tj@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel-team@fb.com
Subject: Re: [PATCH] fs: inode: Recycle inodenum from volatile inode slabs
Date: Fri, 27 Dec 2019 11:37:32 +0000 [thread overview]
Message-ID: <20191227113732.GB442424@chrisdown.name> (raw)
In-Reply-To: <88698fed-528b-85b2-1d07-e00051d6db60@huawei.com>
zhengbin (A) writes:
>How about tmpfs and hugetlbfs use their own get_next_ino? like
>
>static DEFINE_PER_CPU(unsigned int, tmpfs_last_ino),
>
>which can reduce the risk of 32 bit wraparound further.
This won't help by itself, because in the case presented the wraparound almost
solely comes from shmem alone.
next prev parent reply other threads:[~2019-12-27 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 15:48 [PATCH] fs: inode: Recycle inodenum from volatile inode slabs Chris Down
2019-12-26 15:50 ` Chris Down
2019-12-26 15:53 ` [PATCH v2] " Chris Down
2019-12-26 18:04 ` [PATCH] " Amir Goldstein
2019-12-27 2:15 ` zhengbin (A)
2019-12-27 11:37 ` Chris Down [this message]
2019-12-27 11:36 ` Chris Down
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=20191227113732.GB442424@chrisdown.name \
--to=chris@chrisdown.name \
--cc=amir73il@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=jlayton@kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--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).