Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. More stable kernels with partial Dirty Frag fixes

More stable kernels with partial Dirty Frag fixes

Scheduled Pinned Locked Moved Uncategorized
lwnlinuxkernel
6 Posts 3 Posters 9 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • lwn@fedi.lwn.netL This user is from outside of this forum
    lwn@fedi.lwn.netL This user is from outside of this forum
    lwn@fedi.lwn.net
    wrote last edited by
    #1

    More stable kernels with partial Dirty Frag fixes

    https://lwn.net/Articles/1071483/ #LWN #Linux #kernel

    aho@ioc.exchangeA 1 Reply Last reply
    0
    • lwn@fedi.lwn.netL lwn@fedi.lwn.net

      More stable kernels with partial Dirty Frag fixes

      https://lwn.net/Articles/1071483/ #LWN #Linux #kernel

      aho@ioc.exchangeA This user is from outside of this forum
      aho@ioc.exchangeA This user is from outside of this forum
      aho@ioc.exchange
      wrote last edited by
      #2

      @lwn a bit unrelated, the #postgresql performance degradation in the #Linux #kernel 7, has it been fixed (either postgresql or kernel side)?

      tomasv@fosstodon.orgT 1 Reply Last reply
      0
      • aho@ioc.exchangeA aho@ioc.exchange

        @lwn a bit unrelated, the #postgresql performance degradation in the #Linux #kernel 7, has it been fixed (either postgresql or kernel side)?

        tomasv@fosstodon.orgT This user is from outside of this forum
        tomasv@fosstodon.orgT This user is from outside of this forum
        tomasv@fosstodon.org
        wrote last edited by
        #3

        @aho @lwn I don't think so, or at least I'm not aware of a fix. But I also think the workload showing the regression is extremely artificial, and you'll not see the regression for anything remotely realistic.

        aho@ioc.exchangeA 1 Reply Last reply
        0
        • tomasv@fosstodon.orgT tomasv@fosstodon.org

          @aho @lwn I don't think so, or at least I'm not aware of a fix. But I also think the workload showing the regression is extremely artificial, and you'll not see the regression for anything remotely realistic.

          aho@ioc.exchangeA This user is from outside of this forum
          aho@ioc.exchangeA This user is from outside of this forum
          aho@ioc.exchange
          wrote last edited by
          #4

          @tomasv @lwn that's good to hear, as had to upgrade kernel and was a bit worried over a headline I saw some time ago when I didn't really planed on upgrading kernel...

          lwn@fedi.lwn.netL 1 Reply Last reply
          0
          • aho@ioc.exchangeA aho@ioc.exchange

            @tomasv @lwn that's good to hear, as had to upgrade kernel and was a bit worried over a headline I saw some time ago when I didn't really planed on upgrading kernel...

            lwn@fedi.lwn.netL This user is from outside of this forum
            lwn@fedi.lwn.netL This user is from outside of this forum
            lwn@fedi.lwn.net
            wrote last edited by
            #5

            @aho @tomasv This is the article, "The 7.0 scheduler regression that wasn't".

            The tl;dr was that the "regression" happened on a system running PostgreSQL with huge pages disabled. Once the reporter enabled them, the problem disappeared.

            https://lwn.net/Articles/1067029/

            aho@ioc.exchangeA 1 Reply Last reply
            0
            • lwn@fedi.lwn.netL lwn@fedi.lwn.net

              @aho @tomasv This is the article, "The 7.0 scheduler regression that wasn't".

              The tl;dr was that the "regression" happened on a system running PostgreSQL with huge pages disabled. Once the reporter enabled them, the problem disappeared.

              https://lwn.net/Articles/1067029/

              aho@ioc.exchangeA This user is from outside of this forum
              aho@ioc.exchangeA This user is from outside of this forum
              aho@ioc.exchange
              wrote last edited by
              #6

              @lwn @tomasv thanks

              1 Reply Last reply
              1
              0
              • R relay@relay.infosec.exchange shared this topic
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups