linux-kernel - Re: CFQ will be the new default IO scheduler

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <200607241857.43399.a1426z@gawab.com>
Date:	Mon, 24 Jul 2006 18:57:43 +0300
From:	Al Boldi <a1426z@...ab.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-fsdevel@...r.kernel.org
Subject: Re: CFQ will be the new default IO scheduler - why?

Justin Piszcz wrote:
> 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.
>
> Should there be a default scheduler per filesystem?  As some filesystems
> may perform better/worse with one over another?

It's currently perDevice, and should probably be extended to perMount.

Thanks!

--
Al

-
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/