From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>,
Henning Schild <henning.schild@siemens.com>,
"Moessbauer, Felix" <felix.moessbauer@siemens.com>,
Joe MacDonald <joe_macdonald@mentor.com>
Subject: Re: [PATCHSET] expand last partition script and its usage
Date: Fri, 16 Dec 2022 09:14:08 +0100 [thread overview]
Message-ID: <CAJGKYO5Nomn1xf_Xu5w2rFR30f7YXSQGSyO32b+XrqjyNjWJfg@mail.gmail.com> (raw)
In-Reply-To: <CAJGKYO7nHsp0j6dFhFJf9Fn1yKz2R8CLL1Z+voAEcKpUAxryqQ@mail.gmail.com>
On Fri, 16 Dec 2022 at 00:00, Roberto A. Foglietta
<roberto.foglietta@gmail.com> wrote:
>
> Hi all,
> - udev support: udevadm settle is the first task to run
[...]
> - unpartitioned volumes are resized as well (tested)
about these points the latency introduced by udevadm settle is
irrelevant in most cases about 0.1 seconds and because I commented the
code that checks for the free space in the last partition (all
resizing tools do that more efficiently) - in general the execution
time will be smaller - faster. In those platforms in which the boot
time grows up - most probably are the same that would fail because
they boot from a small internal storage device and might use
unpartitioned devices for rootfs or RW. Likely the qemu test that I
presented here in which vmlinuz and initrd image are separated from
the unpartitioned volume. In such a case the mount cannot trigger the
kernel to map the device because rootfs and bootfs are on different
devices. This is also the reason because I denominated the patch
"generalisation" - not only for having added btrfs. That support was
been in place since September 30th.
Best regards, R-
next prev parent reply other threads:[~2022-12-16 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 18:06 Roberto A. Foglietta
2022-12-15 18:27 ` Roberto A. Foglietta
2022-12-15 23:00 ` Roberto A. Foglietta
2022-12-16 8:14 ` Roberto A. Foglietta [this message]
2022-12-16 11:38 ` Roberto A. Foglietta
2022-12-18 13:50 ` Roberto A. Foglietta
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=CAJGKYO5Nomn1xf_Xu5w2rFR30f7YXSQGSyO32b+XrqjyNjWJfg@mail.gmail.com \
--to=roberto.foglietta@gmail.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=joe_macdonald@mentor.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