Sunday, July 31, 2016

BFS 0472 Sync-up patch for 4.7 kernel is available

BFS 0472 Sync-up patch for 4.7 kernel is available after spending the last weekend to put all sync-up patches upon bfs 0472 and fixed the suspend/resume issue on one of my notebook.

Based on quick sanity tests, the cpufreq api deployment issue in 0470 has been fixed. And the performance for low workload is better than previous release.

Enjoy this and wait for the incoming vrq patch. :)


BR Alfred

11 comments:

  1. I see your BFS version differs from Con's one much. But still those are "bare" versions. So what's the point?

    ReplyDelete
    Replies
    1. @post-factum:
      Thank you very much for your notification! Good to know, that someone with knowledge has time to follow the code changes! :-)

      @Alfred:
      You need to answer on this above.

      Besides assuming that you work on the next VRQ, would you find time to backport the significant BFS 470 to 472 improvements for the 4.6 kernel VRQ?
      Reason to ask for this is: I'm not sure how long forward porting of my old TuxOnIce working revision may take or if it may work at all. If in-kernel suspend-to-disk hasn't heavily improved in speed, I won't want to use it without TuxOnIce. Saying: I'd stay with 4.6 kernel until TOI works.

      BR, Manuel Krause

      Delete
    2. Based on 0472, there are additional mainline sync-up patches from release to release that doesn't be pick-up by CK in my "bare" bfs patch. There are the commits in my git branch with "[Sync]" mark-up.

      Consider the cpu hotplug changes and other api changes in 4.7, I don't think it's suitable to back-port to 4.6.

      BR Alfred

      Delete
    3. @Alfred:
      Thank you for the information. Fortunately I was successful with my forward-porting, and as 4.7.0 doesn't make problems on my notebook, I'd stay with it and look forward to your new VRQ implementation. :-)
      What still doesn't work on here is BFQ v8. Lockups after few minutes of uptime (with 4.6.x and 4.7.0 -- while the v7r11, with the omitted 4th patch, works fine). I follow their google group and see others having the problem, too. Let's give Paolo and his great team more time for the new code to mature.

      BR Manuel Krause

      Delete
    4. @Alfred:
      Sorry for bothering -- this should be an encouragement for your continued VRQ work:
      Interactivity with the plain BFS for 4.7.0 from yours is worse than every "bad" usage result with 4.6.x VRQ (+ testXYZ) on here. Just wanted to let you know.

      Your next VRQ is highly appreciated!

      BR Manuel Krause

      Delete
    5. Good news for the people trying to use BFQ v8 and being affected by panics/ lockups:
      The latest commit (on github) / patch (on the google-group) fixes the issue for me and at least one other person.

      BR Manuel Krause

      Delete
    6. @Manuel
      vrq0 patch was out. And would you kindly point out the link for the patch/commit on github? Thought there is no panics/lockups issues here.

      BR Alfred

      Delete
    7. @Alfred:
      Last posting was only regarding possible BFQ issues NOT related to BFS/VRQ.

      Currently I'm re-testing 4.6.5 with VRQtest5 +my TOI port with new BFQ v8 + the relevant patch.

      The links may be:
      Group's topic:
      https://groups.google.com/forum/?fromgroups=#!topic/bfq-iosched/80V4U6ak57w

      Download of the patch:
      https://groups.google.com/group/bfq-iosched/attach/81df4b74080cb/0001-Change-suspect-BUG_ON-and-add-more-BUG_ONs.patch?part=0.1

      On github it's the most recent commit:
      https://github.com/linusw/linux-bfq/commits/bfq-v8-v4.6
      e.g. https://github.com/linusw/linux-bfq/commit/c19158efaebc215298f1b8f82b1df1dce526e1b5
      --- or ---
      https://github.com/linusw/linux-bfq/commits/bfq-v8-v4.7
      e.g. https://github.com/linusw/linux-bfq/commit/da81ffdf83bf5834e63deab5911de32ce255f2fa

      Coming to your 4.7.0 VRQ0 soon, tonight.

      BR Manuel Krause

      Delete
    8. With kernels without this recent BFQ commit my machine usually locked up within 2-7 minutes. It's not happening any more WITH the patch, having some hours of uptime and undergone some TOI hibernations with my experimental port, and so I'd consider it safe.

      BR Manuel Krause

      Delete
  2. Alfred, with 4.5 I've got pretty much the same hang as usual and in pretty short period of time, but this time netconsole did not make any output for me.

    Will wait for another hang. It definitely started since 4.5.

    ReplyDelete
    Replies
    1. @pf
      Thanks for the info. Let's wait for another hang.

      Delete