[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZbQzXfqA5vK5JXZS@casper.infradead.org>
Date: Fri, 26 Jan 2024 22:34:05 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux Trace Devel <linux-trace-devel@...r.kernel.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Christian Brauner <brauner@...nel.org>,
Ajay Kaher <ajay.kaher@...adcom.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH] eventfs: Have inodes have unique inode numbers
On Fri, Jan 26, 2024 at 05:14:12PM -0500, Mathieu Desnoyers wrote:
> I would suggest this straightforward solution to this:
>
> a) define a EVENTFS_MAX_INODES (e.g. 4096 * 8),
>
> b) keep track of inode allocation in a bitmap (within a single page),
>
> c) disallow allocating more than "EVENTFS_MAX_INODES" in eventfs.
.. reinventing the IDA?
Powered by blists - more mailing lists