From: Zdenek Kabelac <zdenek.kabelac@gmail.com> To: LVM general discussion and development <linux-lvm@redhat.com>, Gionatan Danti <g.danti@assyoma.it> Cc: Martin Wilck <martin.wilck@suse.com>, teigland@redhat.com, Heming Zhao <heming.zhao@suse.com> Subject: Re: [linux-lvm] lvmpolld causes high cpu load issue Date: Wed, 17 Aug 2022 20:54:18 +0200 [thread overview] Message-ID: <007c8163-7480-951c-c8b6-78fe47b3a874@gmail.com> (raw) In-Reply-To: <6a1d353d97a6dcdb658affe54b04c1be@assyoma.it> Dne 17. 08. 22 v 19:35 Gionatan Danti napsal(a): > Il 2022-08-17 17:26 Zdenek Kabelac ha scritto: >>> I like the general idea of the udev watch. It is the magic that causes >>> newly created partitions to magically appear in the system, which is > > Would disabling the watch rule be a reasonable approach in this case? If the > user want to scan a new device, it only needs to issue partprobe or kpartx, or > am I missing something? Before diving into these 'deep waters' - I'd really like to first see if the problem is still such an issue with our upstream code base. There have been lot of minor optimization committed over the time - so the amount of fired 'watch' rules should be considerably smaller then the version mentioned in customer issue. >> There is on going 'SID' project - that might push the logic somewhat >> further, but existing 'device' support logic as is today is >> unfortunate 'trace' of how the design should not have been made - and >> since all 'original' programmers left the project long time ago - it's >> non-trivial to push things forward. > > Well, this is not good news. Just for my education, it is possibile to run a > modern linux distro without udev at all? I still remember when the new cool > thing for device autodiscovery was devfs (with some distro - like gentoo - > taking the alternative approach to simply tarrig & untarring much of the > entire /dev/ files to prepopulate the major+minor number... > >> We just hope the SID will make some progress (although probably small >> one at the beginning). > > Any info on the project? https://github.com/prajnoha/sid Zdenek _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://listman.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
WARNING: multiple messages have this Message-ID (diff)
From: Zdenek Kabelac <zdenek.kabelac@gmail.com> To: linux-lvm@redhat.com Cc: Martin Wilck <martin.wilck@suse.com>, teigland@redhat.com, Heming Zhao <heming.zhao@suse.com> Subject: Re: [linux-lvm] lvmpolld causes high cpu load issue Date: Wed, 17 Aug 2022 20:54:18 +0200 [thread overview] Message-ID: <007c8163-7480-951c-c8b6-78fe47b3a874@gmail.com> (raw) Message-ID: <20220817185418.cXNyhanV_cG_W2Qh2FB0zcIZzCqw_nwAQv6BiIQpZg8@z> (raw) In-Reply-To: <6a1d353d97a6dcdb658affe54b04c1be@assyoma.it> Dne 17. 08. 22 v 19:35 Gionatan Danti napsal(a): > Il 2022-08-17 17:26 Zdenek Kabelac ha scritto: >>> I like the general idea of the udev watch. It is the magic that causes >>> newly created partitions to magically appear in the system, which is > > Would disabling the watch rule be a reasonable approach in this case? If the > user want to scan a new device, it only needs to issue partprobe or kpartx, or > am I missing something? Before diving into these 'deep waters' - I'd really like to first see if the problem is still such an issue with our upstream code base. There have been lot of minor optimization committed over the time - so the amount of fired 'watch' rules should be considerably smaller then the version mentioned in customer issue. >> There is on going 'SID' project - that might push the logic somewhat >> further, but existing 'device' support logic as is today is >> unfortunate 'trace' of how the design should not have been made - and >> since all 'original' programmers left the project long time ago - it's >> non-trivial to push things forward. > > Well, this is not good news. Just for my education, it is possibile to run a > modern linux distro without udev at all? I still remember when the new cool > thing for device autodiscovery was devfs (with some distro - like gentoo - > taking the alternative approach to simply tarrig & untarring much of the > entire /dev/ files to prepopulate the major+minor number... > >> We just hope the SID will make some progress (although probably small >> one at the beginning). > > Any info on the project? https://github.com/prajnoha/sid Zdenek _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://listman.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2022-08-17 18:54 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-16 9:28 [linux-lvm] lvmpolld causes IO performance issue Heming Zhao 2022-08-16 9:38 ` Zdenek Kabelac 2022-08-16 10:08 ` [linux-lvm] lvmpolld causes high cpu load issue Heming Zhao 2022-08-16 10:26 ` Zdenek Kabelac 2022-08-17 2:03 ` Heming Zhao 2022-08-17 8:06 ` Zdenek Kabelac 2022-08-17 8:43 ` Heming Zhao 2022-08-17 9:46 ` Zdenek Kabelac 2022-08-17 10:47 ` Heming Zhao 2022-08-17 11:13 ` Zdenek Kabelac 2022-08-17 12:39 ` Martin Wilck 2022-08-17 12:54 ` Zdenek Kabelac 2022-08-17 13:41 ` Martin Wilck 2022-08-17 15:11 ` David Teigland 2022-08-18 8:06 ` Martin Wilck 2022-08-17 15:26 ` Zdenek Kabelac 2022-08-17 15:58 ` Demi Marie Obenour 2022-08-18 7:37 ` Martin Wilck 2022-08-17 17:35 ` Gionatan Danti 2022-08-17 18:54 ` Zdenek Kabelac [this message] 2022-08-17 18:54 ` Zdenek Kabelac 2022-08-17 19:13 ` Gionatan Danti 2022-08-18 21:13 ` Martin Wilck
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=007c8163-7480-951c-c8b6-78fe47b3a874@gmail.com \ --to=zdenek.kabelac@gmail.com \ --cc=g.danti@assyoma.it \ --cc=heming.zhao@suse.com \ --cc=linux-lvm@redhat.com \ --cc=martin.wilck@suse.com \ --cc=teigland@redhat.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: linkBe 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).