On Wed, Dec 24, 2014 at 4:00 AM, Alison Chaiken ali...@she-devel.com wrote:
Tom Gundersen:
In a stock Fedora/Arch (and probably others, but didn't check)
systemd-modules-load is not used at all.
[ . . . ]
I'm not aware of any kernel modules that legitimately needs to be
loaded in this way (i.e.,
2014-12-24 12:58 GMT+01:00 Lucas De Marchi lucas.de.mar...@gmail.com:
On Wed, Dec 24, 2014 at 4:00 AM, Alison Chaiken ali...@she-devel.com wrote:
On my Debian Testing system, I see fuse, loop, lp, ppdev and
parport_pc. The last 3 are related to printing, and presumably must
..
fuse and
2014-12-25 1:59 GMT+01:00 Alison Chaiken ali...@she-devel.com:
Those entries were most likely created by older versions of
debian-installer. The current version of debian-installer for
debian-installer should no longer add fuse or loop to /etc/modules.
Here are the details:
[ .. ]
] Improving module loading
On Sun, Dec 21, 2014 at 12:31:30PM +, Hoyer, Marko (ADITG/SW2)
wrote:
If you have control over your kernel, why not just build the
modules
into the kernel, then all of this isn't an issue at all and there
is
no overhead of module loading
-Original Message-
From: Lucas De Marchi [mailto:lucas.de.mar...@gmail.com]
Sent: Monday, December 22, 2014 7:00 PM
To: Lennart Poettering
Cc: Hoyer, Marko (ADITG/SW2); systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Improving module loading
On Mon, Dec 22, 2014
On Tue, Dec 23, 2014 at 12:25 PM, Hoyer, Marko (ADITG/SW2)
mho...@de.adit-jv.com wrote:
Some numbers to the above mentioned arguments:
- in an idle system, systemd-udev-trigger.service takes by about 150-200ms
just to get the complete device tree to send out add uevents again (udevd
was
@lists.freedesktop.org
Subject: Re: [systemd-devel] Improving module loading
On Mon, Dec 22, 2014 at 1:04 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Sat, 20.12.14 10:45, Hoyer, Marko (ADITG/SW2) (mho...@de.adit-
jv.com) wrote:
I had such a discussion earlier with some of the systemd guys. My
On Tue, Dec 23, 2014 at 12:25 PM, Hoyer, Marko (ADITG/SW2)
mho...@de.adit-jv.com wrote:
Some numbers to the above mentioned arguments:
- in an idle system, systemd-udev-trigger.service takes by about 150-200ms
just to get the complete device tree to send out add uevents again (udevd
was
On Tue, Dec 23, 2014 at 3:22 PM, Tom Gundersen t...@jklm.no wrote:
On Tue, Dec 23, 2014 at 12:25 PM, Hoyer, Marko (ADITG/SW2)
mho...@de.adit-jv.com wrote:
Some numbers to the above mentioned arguments:
- in an idle system, systemd-udev-trigger.service takes by about 150-200ms
just to get the
On Tue, Dec 23, 2014 at 11:25:23AM +, Hoyer, Marko (ADITG/SW2) wrote:
What do you mean by this? What is limiting this? What is your limit?
How large are these kernel modules that you are having a hard time to
build into your kernel image?
- As far as I remember, we have special
Marko Hoyer:
Are you talking about Save To RAM, Save to Disk, or a hybrid combination
of both? Or do you have something
completely different in mind?
GKH:
A number of devices in the past have done a save system image to flash, and
then when starting up, just load the
system image into
On Sat, 20.12.14 10:45, Hoyer, Marko (ADITG/SW2) (mho...@de.adit-jv.com) wrote:
I had such a discussion earlier with some of the systemd guys. My
intention was to introduce an additional unit for module loading for
exactly the reason you mentioned. The following (reasonable) outcome
was:
-
On Mon, Dec 22, 2014 at 1:04 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Sat, 20.12.14 10:45, Hoyer, Marko (ADITG/SW2) (mho...@de.adit-jv.com)
wrote:
I had such a discussion earlier with some of the systemd guys. My
intention was to introduce an additional unit for module loading
-Original Message-
From: Greg KH [mailto:gre...@linuxfoundation.org]
Sent: Saturday, December 20, 2014 6:11 PM
To: Hoyer, Marko (ADITG/SW2)
Cc: Umut Tezduyar Lindskog; systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Improving module loading
On Sat, Dec 20, 2014
-Original Message-
From: Umut Tezduyar Lindskog [mailto:u...@tezduyar.com]
Sent: Saturday, December 20, 2014 6:45 PM
To: Hoyer, Marko (ADITG/SW2)
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Improving module loading
Hi Marko,
Thank you very much for your
-Original Message-
From: systemd-devel [mailto:systemd-devel-
boun...@lists.freedesktop.org] On Behalf Of Tom Gundersen
Sent: Saturday, December 20, 2014 4:57 PM
To: Umut Tezduyar
Cc: systemd Mailing List
Subject: Re: [systemd-devel] Improving module loading
On 16 Dec 2014 17
: [systemd-devel] Improving module loading
[...]
I had such a discussion earlier with some of the systemd guys. My
intention was to introduce an additional unit for module loading for
exactly the reason you mentioned. The following (reasonable) outcome
was:
Do you have links
-Original Message-
From: Ivan Shapovalov [mailto:intelfx...@gmail.com]
Sent: Sunday, December 21, 2014 3:26 PM
To: systemd-devel@lists.freedesktop.org
Cc: Hoyer, Marko (ADITG/SW2); Umut Tezduyar Lindskog
Subject: Re: [systemd-devel] Improving module loading
On Sunday, December 21
On Sun, Dec 21, 2014 at 12:31:30PM +, Hoyer, Marko (ADITG/SW2) wrote:
If you have control over your kernel, why not just build the modules
into the kernel, then all of this isn't an issue at all and there is no
overhead of module loading?
It is a questions of kernel image size and
Hi,
-Original Message-
From: systemd-devel [mailto:systemd-devel-
boun...@lists.freedesktop.org] On Behalf Of Umut Tezduyar Lindskog
Sent: Tuesday, December 16, 2014 4:55 PM
To: systemd-devel@lists.freedesktop.org
Subject: [systemd-devel] Improving module loading
Hi
On 16 Dec 2014 17:21, Umut Tezduyar Lindskog u...@tezduyar.com wrote:
On Tue, Dec 16, 2014 at 4:59 PM, Tom Gundersen t...@jklm.no wrote:
On Tue, Dec 16, 2014 at 4:54 PM, Umut Tezduyar Lindskog
u...@tezduyar.com wrote:
The other thought is, what is the preferred way of loading modules
@lists.freedesktop.org
Subject: [systemd-devel] Improving module loading
Hi,
Is there a reason why systemd-modules-load is loading modules
sequentially? Few things can happen simultaneously like resolving the
symbols etc. Seems like modules_mutex is common on module loads which
gets locked up
Sent: Tuesday, December 16, 2014 4:55 PM
To: systemd-devel@lists.freedesktop.org
Subject: [systemd-devel] Improving module loading
Hi,
Is there a reason why systemd-modules-load is loading modules
sequentially? Few things can happen simultaneously like resolving the
symbols etc
: Tuesday, December 16, 2014 4:55 PM
To: systemd-devel@lists.freedesktop.org
Subject: [systemd-devel] Improving module loading
Hi,
Is there a reason why systemd-modules-load is loading modules
sequentially? Few things can happen simultaneously like resolving the
symbols etc. Seems like modules_mutex
[mailto:systemd-devel-
boun...@lists.freedesktop.org] On Behalf Of Umut Tezduyar Lindskog
Sent: Tuesday, December 16, 2014 4:55 PM
To: systemd-devel@lists.freedesktop.org
Subject: [systemd-devel] Improving module loading
Hi,
Is there a reason why systemd-modules-load is loading modules
On Tue, Dec 16, 2014 at 4:54 PM, Umut Tezduyar Lindskog
u...@tezduyar.com wrote:
The other thought is, what is the preferred way of loading modules
when they are needed.
Rely on kernel autoloading. Not all modules support that yet, but most
do. What do you have in mind?
Do they have to be
On Tue, Dec 16, 2014 at 4:59 PM, Tom Gundersen t...@jklm.no wrote:
On Tue, Dec 16, 2014 at 4:54 PM, Umut Tezduyar Lindskog
u...@tezduyar.com wrote:
The other thought is, what is the preferred way of loading modules
when they are needed.
Rely on kernel autoloading. Not all modules support
On 12/16/2014 03:54 PM, Umut Tezduyar Lindskog wrote:
Hi,
Is there a reason why systemd-modules-load is loading modules
sequentially? Few things can happen simultaneously like resolving the
symbols etc. Seems like modules_mutex is common on module loads which
gets locked up on few occasions
28 matches
Mail list logo
