From: Li Wang <liwang@redhat.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: "Darrick J . Wong" <djwong@kernel.org>,
linux-xfs@vger.kernel.org, LTP List <ltp@lists.linux.it>,
automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] [RFC PATCH 1/1] API: Allow to use xfs filesystems < 300 MB
Date: Mon, 29 Aug 2022 09:45:50 +0800 [thread overview]
Message-ID: <CAEemH2e_t5XdGNFPOw0suGgAEbWLYPuX-tnZCoxQ1oZJZ9H2pg@mail.gmail.com> (raw)
In-Reply-To: <YwX7r5VWrGRzaXoa@pevik>
[-- Attachment #1.1: Type: text/plain, Size: 598 bytes --]
Hi Petr, All,
Petr Vorel <pvorel@suse.cz> wrote:
> Hi all,
>
> Could we in the end accept this patch?
>
> It'd fix the issue for now and I could set size of the XFS loop device
> smaller
> than 300 MB (better for embedded). i.e. 16 MB (or 32 or 64 MB or anything
> higher
> if XFS developers are convinced it's needed).
>
I personally think YES!
(sorry for replying so late, I was on vacation last week)
>
> As I wrote before I plan to suggest sizes:
> btrfs 110 MB
> the rest (ext[234], xfs, ntfs, vfat, exfat, tmpfs): 16 MB
>
+1 thanks for finding the minimal size.
--
Regards,
Li Wang
[-- Attachment #1.2: Type: text/html, Size: 1494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 60 bytes --]
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-08-29 1:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 20:40 [LTP] [RFC PATCH 1/1] API: Allow to use xfs filesystems < 300 MB Petr Vorel
2022-08-17 23:59 ` Darrick J. Wong
2022-08-18 5:08 ` Amir Goldstein
2022-08-18 9:45 ` Petr Vorel
2022-08-18 9:01 ` Petr Vorel
2022-08-18 9:53 ` Cyril Hrubis
2022-08-18 11:12 ` Petr Vorel
2022-08-18 11:30 ` Cyril Hrubis
2022-08-18 11:55 ` [LTP] [Automated-testing] " Geert Uytterhoeven
2022-08-19 19:28 ` Petr Vorel
2022-08-20 2:37 ` Li Wang
2022-08-22 9:36 ` Petr Vorel
2022-08-20 2:52 ` [LTP] " Li Wang
2022-08-24 10:21 ` Petr Vorel
2022-08-29 1:45 ` Li Wang [this message]
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=CAEemH2e_t5XdGNFPOw0suGgAEbWLYPuX-tnZCoxQ1oZJZ9H2pg@mail.gmail.com \
--to=liwang@redhat.com \
--cc=automated-testing@lists.yoctoproject.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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).