Err, zram ofc :)
//M
Sent from my BlackBerry — the most secure mobile device
Original Message
From: [email protected]
Sent: 3 May 2019 23:14
To: [email protected]; [email protected]
Subject: Re: [PATCH 0/3] mdev: add daemon mode
Or even better you could turn on zswap on your embedded device and avoid the
OOM-kiler which I guess is the real reason you fixed this.
Actually I want to know when this happens that the kernel creates that many
hotplug events; seems like the issue is somewhere else.
//M
Sent from my BlackBerry — the most secure mobile device
Original Message
From: [email protected]
Sent: 3 May 2019 23:03
To: [email protected]
Subject: [PATCH 0/3] mdev: add daemon mode
If mdev is used as kernel hotplug helper and the system generates many
hotplug events it will quickly consume considerable resources because a
process is forked for each event and, if the mdev.seq feature is used,
they must also coordinate among each other. While the uevent applet
mitigates some of the resource problems you still have to pay the cost
for a fork/exec and parsing of mdev.conf for each event.
The following patches add an optional daemon mode to mdev that let's
mdev listen on a netlink socket for kernel hotplug events. This mode
works much like udev and avoids the fork/exec/parse overhead on many
events.
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
