From: Martin Wilck <martin.wilck@suse.com>
To: Heming Zhao <heming.zhao@suse.com>,
"demi@invisiblethingslab.com" <demi@invisiblethingslab.com>,
"linux-lvm@redhat.com" <linux-lvm@redhat.com>
Cc: "teigland@redhat.com" <teigland@redhat.com>
Subject: Re: [linux-lvm] lvmpolld causes high cpu load issue
Date: Thu, 18 Aug 2022 07:37:00 +0000 [thread overview]
Message-ID: <d8233dee5724f77974790d8940ef33518f037d42.camel@suse.com> (raw)
In-Reply-To: <Yv0QQrK/B23/06oC@itl-email>
On Wed, 2022-08-17 at 11:58 -0400, Demi Marie Obenour wrote:
> >
> > 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.
This is almost guaranteed to open up big can of new issues. I can see
that diskseq makes sense for loop devices, but general dm is a very
different issue. Not to say that changing the device names would be
nightmare.
Martin
_______________________________________________
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-23 8:28 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 [this message]
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=d8233dee5724f77974790d8940ef33518f037d42.camel@suse.com \
--to=martin.wilck@suse.com \
--cc=demi@invisiblethingslab.com \
--cc=heming.zhao@suse.com \
--cc=linux-lvm@redhat.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).