From: Al Viro <viro@zeniv.linux.org.uk>
To: Matthew Wilcox <willy@infradead.org>
Cc: Bruno Haible <bruno@clisp.org>,
Evgeniy Dushistov <dushistov@mail.ru>,
linux-fsdevel@vger.kernel.org
Subject: Re: ufs filesystem cannot mount NetBSD/arm64 partition
Date: Mon, 15 Jan 2024 23:25:09 +0000 [thread overview]
Message-ID: <20240115232509.GJ1674809@ZenIV> (raw)
In-Reply-To: <ZaW6/bFaN9HEANW+@casper.infradead.org>
On Mon, Jan 15, 2024 at 11:08:45PM +0000, Matthew Wilcox wrote:
> Wouldn't surprise me if netbsd/arm64 had decided to go with 64kB
> PAGE_SIZE and 8kB fragments ...
>
> > FWIW, theoretically it might be possible to make that comparison with
> > PAGE_SIZE instead of 4096 and require 16K or 64K pages for the kernel
> > in question; that ought to work, modulo bugs in completely untested
> > cases ;-/
> >
> > Support with 4K pages is a different story - that would take much
> > more surgery in fs/ufs.
>
> Possibly not too much more. With large folios, we're most of the way
> to being able to support this. If there's real interest, we can look
> at supporting large folios in UFS.
Metadata handling will take some work. I've done some untangling in
prep to that (see #work.ufs), but that's not all. And fun around
tail unpacking is also not quite there.
next prev parent reply other threads:[~2024-01-15 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 22:05 ufs filesystem cannot mount NetBSD/arm64 partition Bruno Haible
2024-01-15 22:22 ` Al Viro
2024-01-15 22:33 ` Al Viro
2024-01-15 23:08 ` Matthew Wilcox
2024-01-15 23:25 ` Al Viro [this message]
2024-01-15 23:29 ` Bruno Haible
2024-01-15 23:36 ` Al Viro
2024-01-15 23:28 ` Bruno Haible
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=20240115232509.GJ1674809@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=bruno@clisp.org \
--cc=dushistov@mail.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.org \
/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).