Re: [PATCH block:for-3.3/core] cfq: merged request shouldn't jump to a different cfqq

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jan 5, 2012 at 7:34 PM, Shaohua Li <shaohua.li@xxxxxxxxx> wrote:
>> That's how cfq has behaved before this recent plug merge breakage and
>> IIRC why the cooperating queue thing is there.  If you want to change
>> the behavior, that should be an explicit separate patch.
> My point is both cooperating merge and the plug merge of different cfq
> are merge, no reason we allow one but disallow the other. plug merge
> isn't a breakage to me.

Isolation is pretty big deal for cfq and cross cfqq merging happening
without cfq noticing it isn't gonna be helpful to the cause.  Why
don't we merge bio's across different cfqq's then?

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux