Results 1 to 5 of 5

Thread: Updating the kernel minding the BFQ kmp version from tiwai repo

  1. #1

    Question Updating the kernel minding the BFQ kmp version from tiwai repo

    First of all, apologies if I posted this in the wrong section.

    I've recently started using BFQ scheduler from Takashi Iwai's repo. Tumbleweed kernel update will inevitably make the BFQ scheduler module inactive.

    The problem:
    Have BFQ kmp built for 4.9.0,
    TW updates to kernel-default 4.9.3.
    -> BFQ is uninstalled because nothing provides kernel-default 4.9.0

    My question is: is it possible to protect the BFQ scheduler module and only allow kernel update when mr. Iwai catches up to the current kernel version? If so, how would I go about doing this?

  2. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,144
    Blog Entries
    2

    Default Re: Updating the kernel minding the BFQ kmp version from tiwai repo

    Typically,
    I've seen the command to invoke a specific disk scheduler placed in /etc/sysctl.conf

    Generally speaking,
    I've found that any settings in /etc/sysctl.conf reloads and over-writes default system configurations, this means that no matter what happens during a reboot, it will be overwritten using the commands in sysctl.conf
    I wrote a paper a long time ago (still valid) on setting custom values for networking resources using this method

    https://sites.google.com/site/4techs...orithm-changes

    Looks like others have written about this, too, Google "setting disk scheduler sysctl"

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  3. #3

    Default Re: Updating the kernel minding the BFQ kmp version from tiwai repo

    Quote Originally Posted by tsu2 View Post
    Typically,
    I've seen the command to invoke a specific disk scheduler placed in /etc/sysctl.conf

    Generally speaking,
    I've found that any settings in /etc/sysctl.conf reloads and over-writes default system configurations, this means that no matter what happens during a reboot, it will be overwritten using the commands in sysctl.conf
    I wrote a paper a long time ago (still valid) on setting custom values for networking resources using this method

    https://sites.google.com/site/4techs...orithm-changes

    Looks like others have written about this, too, Google "setting disk scheduler sysctl"

    TSU
    Setting the disk scheduler is not the issue here. Let's generalize the problem:

    I have package A that depends on package B having a specific version. Package B updates faster than package A. How do I go about locking package B update until package A catches up to it?

  4. #4
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,674
    Blog Entries
    15

    Default Re: Updating the kernel minding the BFQ kmp version from tiwai repo

    Hi
    I'm assuming your grabbing it from;
    http://download.opensuse.org/reposit...nSUSE-Factory/

    Use zypper to add a lock (zypper al) to the kernel so this doesn't update, then when it rebuilds in the above repo to the new release, remove the lock, update and then after reboot, lock the kernel again...

    If it's the same kernel though, eg 4.9 series, updating the kernel will move the kmp into the weak-updates directory (check with /sbin/moding bfq | grep file, so should keep working until the kmp catches up...
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  5. #5

    Default Re: Updating the kernel minding the BFQ kmp version from tiwai repo

    Quote Originally Posted by malcolmlewis View Post
    Hi
    I'm assuming your grabbing it from;
    http://download.opensuse.org/reposit...nSUSE-Factory/

    Use zypper to add a lock (zypper al) to the kernel so this doesn't update, then when it rebuilds in the above repo to the new release, remove the lock, update and then after reboot, lock the kernel again...

    If it's the same kernel though, eg 4.9 series, updating the kernel will move the kmp into the weak-updates directory (check with /sbin/moding bfq | grep file, so should keep working until the kmp catches up...
    Yes, that's the repo I'm using. I've suspected this will be the answer, but I wanted to confirm with people more experienced and knowledgable first.
    Thank you

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •