[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20131025082043.GA1418@quack.suse.cz>
Date: Fri, 25 Oct 2013 10:20:43 +0200
From: Jan Kara <jack@...e.cz>
To: 韩磊 <bonben1989@...il.com>
Cc: Jan Kara <jack@...e.cz>, linux-kernel@...r.kernel.org
Subject: Re: A thought about IO scheduler in linux kernel for SSD
On Fri 25-10-13 11:10:22, 韩磊 wrote:
> 2013/10/23 Jan Kara <jack@...e.cz>:
> > On Wed 23-10-13 08:47:44, 韩磊 wrote:
> >> Nowadays,the IO schedulers in linux kernel have four types:
> >>
> >> deadline,noop,Anticiptory and CFQ.CFQ is the default scheduler.But CFQ is
> >> not a good scheduler for SSD,dealine may be a good choice.
> >
> > That doesn't make much sense to me. If there are two bios in flight for
> > some sector, results are undefined. Thus we usually avoid such situation
> > (usually we want to have defined contents of the disk :). The exclusion is
> > usually achieved at higher level using page locking etc. So adding code
> > speeding up such requests doesn't seem worth it.
> >
> > Honza
> > --
> > Jan Kara <jack@...e.cz>
> > SUSE Labs, CR
>
> Do you mean that the probability of two bios have the same start
> sector in request list at this level is very low?
Yes, that's exactly what I mean. As Ming Lei notes, there are ways how it
could happen (most notably any direct IO user can generate arbitrary number
of bios with the same start sectors). But in none of these cases
performance matters, it is usually a bug in application if that happens.
Bye
Honza
--
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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