Jump to content

Talk:Completely fair queueing

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
(Redirected from Talk:CFQ)

For Which disk?

[edit]

It is unclear where we can benefit from the deadline scheduler. I'm running my Ubuntu from a flashdisk (USB) and would like to know if this scheduling is an improvement on a USB disk (which has low read latency, but extremely high write and random R/W latency). It would be cool to mention if this sceduler is aimed for RAID, HD, SSD, SD or USB Flash or ....

[edit]

Hello fellow Wikipedians,

I have just modified one external link on CFQ. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 10:34, 14 December 2017 (UTC)[reply]

Evolution of CFQ

[edit]

Is Budget Fair Queueing (BFQ) considered to be the next evolutionary step from Completely Fair Queueing (CFQ)? 0dorkmann (talk) 07:56, 4 January 2023 (UTC)[reply]