Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932411AbbG1Odt (ORCPT ); Tue, 28 Jul 2015 10:33:49 -0400 Received: from mail-ig0-f170.google.com ([209.85.213.170]:33583 "EHLO mail-ig0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755702AbbG1Odq (ORCPT ); Tue, 28 Jul 2015 10:33:46 -0400 Message-ID: <55B792C9.2000605@kernel.dk> Date: Tue, 28 Jul 2015 08:33:45 -0600 From: Jens Axboe User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 To: Christoph Hellwig CC: "Martin K. Petersen" , Neil Brown , Liu Bo , linux-raid@vger.kernel.org, dm-devel@redhat.com, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] block: add a bi_error field to struct bio References: <1437398977-8492-1-git-send-email-hch@lst.de> <1437398977-8492-2-git-send-email-hch@lst.de> <55AFE643.5000704@kernel.dk> <55B01252.90004@kernel.dk> <20150724104946.GA25145@lst.de> <55B2699D.6010400@kernel.dk> <20150728111249.GA19647@lst.de> In-Reply-To: <20150728111249.GA19647@lst.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1139 Lines: 26 On 07/28/2015 05:12 AM, Christoph Hellwig wrote: > On Fri, Jul 24, 2015 at 10:36:45AM -0600, Jens Axboe wrote: >> Right, I don't think we need to do that though. If you look at the flags >> usage, it's all over the map. Some use test/set_bit, some set it just by >> OR'ing the mask. There's no reason we can't make this work without relying >> on set/test_bit, and then shrink it to an unsigned int. > > Yes, the current mess doesn't look kosher. The bvec pool bits don't > really make it better. > > But do we really need the cmpxchg hack? Seems like most flags aren't > exposed to concurrency at all, althugh this would need a careful audit. I actually don't think that we do need it at all. With the uptodate bit gone, we really should not have any concurrency issues on it at all. CHAIN and REFFED need serialization, but that is already done previous to this change. -- 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/