Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758016AbbBEQyc (ORCPT ); Thu, 5 Feb 2015 11:54:32 -0500 Received: from mail-lb0-f178.google.com ([209.85.217.178]:51163 "EHLO mail-lb0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753616AbbBEQya (ORCPT ); Thu, 5 Feb 2015 11:54:30 -0500 MIME-Version: 1.0 In-Reply-To: <20131024094948.GT14598@kernel.dk> References: <1382606764-8309-1-git-send-email-axboe@kernel.dk> <1382606764-8309-6-git-send-email-axboe@kernel.dk> <20131024094600.GS14598@kernel.dk> <20131024094713.GA17840@infradead.org> <20131024094948.GT14598@kernel.dk> From: Mike Snitzer Date: Thu, 5 Feb 2015 11:54:08 -0500 X-Google-Sender-Auth: eOT3nbxoHACh0AYVS88KRZ3fxZU Message-ID: Subject: Re: [PATCH 05/11] direct-io: only inc/dec inode->i_dio_count for file systems To: Jens Axboe Cc: Christoph Hellwig , "linux-kernel@vger.kernel.org" , Al Viro Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1086 Lines: 22 On Thu, Oct 24, 2013 at 5:49 AM, Jens Axboe wrote: > On Thu, Oct 24 2013, Christoph Hellwig wrote: >> On Thu, Oct 24, 2013 at 10:46:00AM +0100, Jens Axboe wrote: >> > On Thu, Oct 24 2013, Jens Axboe wrote: >> > > We don't need truncate protection for block devices, so add a flag >> > > bypassing this cache line dirtying twice for every IO. This easily >> > > contributes to 5-10% of the CPU time on high IOPS O_DIRECT testing. >> > >> > There's a merge error in this patch, please find the correct one below. >> >> Btw, I think this patch should not go in with this series but rather via >> the VFS tree as it's not related to the blk-mq infrastructure at all. > > That'd be fine with me, if Al could pick it up if he agrees with it. > Feel free to add an acked/review-by :-) This patch never got picked up. Can it be? -- 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/