Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752397Ab2HCCKj (ORCPT ); Thu, 2 Aug 2012 22:10:39 -0400 Received: from mail-ee0-f46.google.com ([74.125.83.46]:56175 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751588Ab2HCCKf (ORCPT ); Thu, 2 Aug 2012 22:10:35 -0400 MIME-Version: 1.0 In-Reply-To: References: <20120316073213.656519005@fusionio.com> <20120316073512.485027511@fusionio.com> <20120320162157.GE17071@redhat.com> <4F69C62C.7020604@kernel.org> <20120620085724.GA26295@infradead.org> Date: Fri, 3 Aug 2012 10:10:34 +0800 X-Google-Sender-Auth: 64SxcSz3b9aW2cZKAICu525fnlo Message-ID: Subject: Re: [patch 1/2]block: handle merged discard request From: Shaohua Li To: "Martin K. Petersen" Cc: Christoph Hellwig , Vivek Goyal , axboe@kernel.dk, linux-kernel@vger.kernel.org, neilb@suse.de Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 930 Lines: 23 2012/6/22 Martin K. Petersen : >>>>>> "Christoph" == Christoph Hellwig writes: > >>> There are several additional commands in the pipeline where the 1:1 >>> mapping between DMA size and block range is invalid. I want to get >>> rid of the 1:1 assumption in general so we can handle any command >>> without these evil workarounds. > > Christoph> What's the progress on getting these issues sorted out? > > This has bitrotted for a while. I'll put it on my list. I should finally > have some bandwidth again next week... Any update on this? If this will not happen soon, should we just disable discard request merge now? Thanks, Shaohua -- 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/