public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] QoS: Do not try to unload any kernel modules
Date: Fri, 19 Nov 2021 07:26:17 +0100	[thread overview]
Message-ID: <746343b1-e7c5-15d7-b211-d4b054e54850@ipfire.org> (raw)
In-Reply-To: <85DE1A5F-AB09-4531-A2A8-2713D3A4DB55@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]

Hello Michael,

thanks for your reply.

This makes sense to me.

Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>

Thanks, and best regards,
Peter Müller


> Hello,
> 
>> On 17 Nov 2021, at 20:15, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>
>> Hello Michael,
>>
>> could you elaborate more on this one?
> 
> Sure.
> 
>> From my basic understanding, QoS should not try to unload kernel modules indeed,
>> but I did not get why it was doing so in the first place.
> 
> Unloading kernel modules used to be an old thing to do. I have no idea really why what the motivation was.
> 
> Partly to save memory, and partly to not have unused module loaded since hardware for example was being detected by loading every single module and see if it recognised any hardware.
> 
> Here we unload the HTB scheduler simply because we do not need it any more after the QoS was stopped. However, during an update, it might happen that the QoS needs to be restarted. When the kernel has been updated in the same updater, we no longer have the kernel modules available for the running kernel. Since sch_htb was unloaded, we can no longer load it again. That was the motivation for this patch here. At least QoS continues to work until the system is being rebooted after the update.
> 
> Does this make sense?
> 
> -Michael
> 
>>
>> Thanks, and best regards,
>> Peter Müller
>>
>>
>>> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
>>> ---
>>>  config/qos/makeqosscripts.pl | 2 --
>>>  1 file changed, 2 deletions(-)
>>> diff --git a/config/qos/makeqosscripts.pl b/config/qos/makeqosscripts.pl
>>> index 0694bb78c..3234ab366 100644
>>> --- a/config/qos/makeqosscripts.pl
>>> +++ b/config/qos/makeqosscripts.pl
>>> @@ -510,8 +510,6 @@ print <<END
>>>  	iptables -t mangle --flush  QOS-INC >/dev/null 2>&1
>>>  	iptables -t mangle --delete-chain QOS-INC >/dev/null 2>&1
>>>  -	rmmod sch_htb >/dev/null 2>&1
>>> -
>>>  	for i in \$(ls \$RRDLOG/class_*.rrd); do
>>>  		rrdtool update \$i \$(date +%s):
>>>  	done
> 

      reply	other threads:[~2021-11-19  6:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 10:53 Michael Tremer
2021-11-17 20:15 ` Peter Müller
2021-11-18 11:14   ` Michael Tremer
2021-11-19  6:26     ` Peter Müller [this message]

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=746343b1-e7c5-15d7-b211-d4b054e54850@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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