From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alasdair G Kergon Subject: Re: [PATCH 20/20] dm-crypt: sort writes Date: Tue, 21 Aug 2012 11:57:48 +0100 Message-ID: <20120821105748.GB29183@agk-dp.fab.redhat.com> References: <55cef4f342136f3b57d7449b88b4eb1fc6fc7569.1345477953.git.mbroz@redhat.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <55cef4f342136f3b57d7449b88b4eb1fc6fc7569.1345477953.git.mbroz@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: device-mapper development Cc: Mikulas Patocka , Milan Broz List-Id: dm-devel.ids On Tue, Aug 21, 2012 at 11:09:31AM +0200, Mikulas Patocka wrote: > In theory the sorting should be performed by the underlying disk scheduler, > however, in practice the disk scheduler accepts and sorts only 128 requests. > In order to sort more requests, we need to implement our own sorting. Why 128? Isn't this nr_requests? (I thought we discussed this before.) Alasdair