| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <Pine.LNX.4.64.0607240840560.1094@p34.internal.lan> Date: Mon, 24 Jul 2006 08:41:37 -0400 (EDT) From: Justin Piszcz <jpiszcz@...idpixels.com> To: Matthias Andree <matthias.andree@....de> cc: Paa Paa <paapaa125@...mail.com>, linux-kernel@...r.kernel.org Subject: Re: CFQ will be the new default IO scheduler - why? On Mon, 24 Jul 2006, Matthias Andree wrote: > On Sun, 23 Jul 2006, Paa Paa wrote: > >> The default IO scheduler in 2.6.18 will be CFQ (Complete Fair Queuing) >> instead of AS (Anticipatory Scheduler) as described here: >> http://wiki.kernelnewbies.org/Linux_2_6_18. I tried to find (here, at lkml) >> the discussion about this change with no luck. > > That wiki document nicely shows the advantage of the scheduler, namely > that you have "ionice", which isn't possible for AS or Deadline > Schedulers - this allows the operating system to run processes like > updatedb with "nice I/O", meaning these hold when you're doing other > I/O. > > -- > Matthias Andree > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > Should there be a default scheduler per filesystem? As some filesystems may perform better/worse with one over another? Justin. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists