Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754552AbbGXQgt (ORCPT ); Fri, 24 Jul 2015 12:36:49 -0400 Received: from mail-ig0-f176.google.com ([209.85.213.176]:35333 "EHLO mail-ig0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753183AbbGXQgr (ORCPT ); Fri, 24 Jul 2015 12:36:47 -0400 Message-ID: <55B2699D.6010400@kernel.dk> Date: Fri, 24 Jul 2015 10:36: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> In-Reply-To: <20150724104946.GA25145@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: 942 Lines: 21 On 07/24/2015 04:49 AM, Christoph Hellwig wrote: > On Wed, Jul 22, 2015 at 03:59:46PM -0600, Jens Axboe wrote: >> One possible solution would be to shrink bi_flags to an unsigned int, no >> problems fitting that in. Then we could stuff bi_error in that (new) hole, >> and we would end up having the same size again. > > As long as we use set/test/clear_bt on bi_flags that won't work unfortunately. 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. -- 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/