From: Demi Marie Obenour <demi@invisiblethingslab.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Martin Wilck <martin.wilck@suse.com>,
Heming Zhao <heming.zhao@suse.com>
Cc: "teigland@redhat.com" <teigland@redhat.com>
Subject: Re: [linux-lvm] lvmpolld causes high cpu load issue
Date: Wed, 17 Aug 2022 11:58:58 -0400 [thread overview]
Message-ID: <Yv0QQrK/B23/06oC@itl-email> (raw)
In-Reply-To: <6be41a4e-9764-03ba-7231-911c733ffecd@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Wed, Aug 17, 2022 at 05:26:08PM +0200, Zdenek Kabelac wrote:
> Dne 17. 08. 22 v 15:41 Martin Wilck napsal(a):
> > On Wed, 2022-08-17 at 14:54 +0200, Zdenek Kabelac wrote:
> > > Dne 17. 08. 22 v 14:39 Martin Wilck napsal(a):
> > >
> > >
> > > Let's make clear we are very well aware of all the constrains
> > > associated with
> > > udev rule logic (and we tried quite hard to minimize impact -
> > > however udevd
> > > developers kind of 'misunderstood' how badly they will be impacting
> > > system's
> > > performance with the existing watch rule logic - and the story kind
> > > of
> > > 'continues' with 'systemd's' & dBus services unfortunatelly...
> >
> > I dimly remember you dislike udev ;-)
>
> Well it's not 'a dislike' from my side - but the architecture alone is just
> missing in many areas...
>
> Dave is a complete disliker of udev & systemd all together :)....
I find udev useful for physical devices, but for virtual devices it is a
terrible fit. It is far too slow and full of race conditions.
Ideally, device-mapper ioctls would use diskseq instead of major+minor
number everywhere, and devices would be named after the diskseq.
> > 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
>
> Tragedy of design comes from the plain fact that there are only 'very
> occasional' consumers of all these 'collected' data - but gathering all the
> info and keeping all of it 'up-to-date' is getting very very expensive and
> can basically 'neutralize' a lot of your CPU if you have too many resources
> to watch and keep update.....
>
>
> > very convenient for users and wouldn't work otherwise. I can see that
> > it might be inappropriate for LVM PVs. We can discuss changing the
> > rules such that the watch is disabled for LVM devices (both PV and LV).
>
> It's really not fixable as is - since of the complete lack of 'error'
> handling of device in udev DB (i.e. duplicate devices...., various frozen
> devices...)
>
> 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.
What is the SID project, what are its goals, and how does it plan to
achieve them?
- --
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEdodNnxM2uiJZBxxxsoi1X/+cIsEFAmL9EEEACgkQsoi1X/+c
IsEkLhAA0/7E1rP44bEFCK76JzKvevdlxe7sRBEPvgn/1m9SiEntC47QiEjnQeNi
cI9RLmHUlpYRghfDQMq8vhKk6a+NbnGsWTx3jciqQph+5SSIfPW9VuNi9w0nlvwS
GPHLweMadCblWqXh8XP2RvJx1Z1QeXZ6kYbfMjhZdxY7a/vg0rXTh0XghSyrgfYs
lgFbcqdJbEX5q70OGds8rhxAbTiBKnPHh3z5aFTCN7ILXO4blRWcqhDvAk0w3SQf
lt5WgDBjZ+5gv2pNiNuwZIzqsgL6FDE4CcR+7JWlAakC1GcocVp87aoiR1hNGMob
ZQoGaivvIjqYwSkWUDUArS8ntcKRBr/mYBcm6WuGZFbWja6NT2tEVJ8vcXdr2x5W
DoPk7Vkj/Y9pOn2kcYQMKR1mGOQhq1AwimSHuzPOeWifUWM5BOkH7hS46Tyq2bZJ
BM/QjUQcnckyAgPRYu+OWP3IvfOU+bFdTKabaoNgtCT85mfgL65sr8kx23ikQeZb
RQ9VcbQnJceKrNsqBnCDE4Xegh96er4Gm+68Crdgs0adHOTcyC5937PPSVy99ls8
MbkdPEVGHe4L1TS8XhI6+NCf0oaFCVE/1vKeS4yO28VbSn/N3pbhiNF6cpc0sWDg
NA0mbIsl19t4j8CtXVCjPeh1+RULvXqhedQIC/xJF3FserAInkc=
=J7YY
-----END PGP SIGNATURE-----
_______________________________________________
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 16:19 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 [this message]
2022-08-18 7:37 ` Martin Wilck
2022-08-17 17:35 ` Gionatan Danti
2022-08-17 18:54 ` Zdenek Kabelac
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=Yv0QQrK/B23/06oC@itl-email \
--to=demi@invisiblethingslab.com \
--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: 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).