Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 23 Sep 2002 03:11:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 23 Sep 2002 03:11:34 -0400 Received: from ns.virtualhost.dk ([195.184.98.160]:39912 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id ; Mon, 23 Sep 2002 03:11:34 -0400 Date: Mon, 23 Sep 2002 09:16:33 +0200 From: Jens Axboe To: Andrew Morton Cc: lkml , "linux-mm@kvack.org" Subject: Re: 2.5.38-mm2 Message-ID: <20020923071633.GA15479@suse.de> References: <3D8E96AA.C2FA7D8@digeo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D8E96AA.C2FA7D8@digeo.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1124 Lines: 29 On Sun, Sep 22 2002, Andrew Morton wrote: > +read-latency.patch > > Fix the writer-starves-reader elevator problem. This is basically > the read_latency2 patch from -ac kernels. > > On IDE it provides a 100x improvement in read throughput when there > is heavy writeback happening. 40x on SCSI. You need to disable Ah interesting. I do still think that it is worth to investigate _why_ both elevator_linus and deadline does not prevent the read starvation. The read-latency is a hack, not a solution imo. > tagged command queueing on scsi - it appears to be quite stupidly > implemented. Ahem I think you are being excessively harsh, or maybe passing judgement on something you haven't even looked at. Did you consider that you _drive_ may be the broken component? Excessive turn-around times for request when using deep tcq is not unusual, by far. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/