Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755697AbaKRRQf (ORCPT ); Tue, 18 Nov 2014 12:16:35 -0500 Received: from mail-qc0-f178.google.com ([209.85.216.178]:60731 "EHLO mail-qc0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754159AbaKRRQd (ORCPT ); Tue, 18 Nov 2014 12:16:33 -0500 Date: Tue, 18 Nov 2014 12:16:28 -0500 From: Tejun Heo To: Azat Khuzhin Cc: Jens Axboe , Alexander Viro , Christoph Hellwig , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Andrew Morton Subject: Re: [PATCH vfs 1/2] lib: implement ptrset Message-ID: <20141118171628.GA434@htj.dyndns.org> References: <20141113220927.GF2598@htj.dyndns.org> <20141118155629.GV10766@azat> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141118155629.GV10766@azat> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Tue, Nov 18, 2014 at 06:56:29PM +0300, Azat Khuzhin wrote: > On Thu, Nov 13, 2014 at 05:09:27PM -0500, Tejun Heo wrote: > > +int ptrset_add(void *ptr, struct ptrset *set, gfp_t gfp) > > +{ > > + struct ptrset_elem *elem; > > + struct rb_node *parent, **slot; > > + > > + elem = kmalloc(sizeof(*elem), gfp); > > + if (!elem && !in_interrupt()) /* see ptrset_preload() */ > > + elem = this_cpu_xchg(ptrset_preload_elem, NULL); > > + if (!elem) > > + return -ENOMEM; > > + elem->ptr = ptr; > > + > > + if (ptrset_find_slot(elem->ptr, set, &slot, &parent)) { > > + kfree(elem); > > + return -EEXIST; > > + } > > Maybe allocation *after* ptrset_find_slot() will be better? > This will avoid extra kmalloc/kfree if such ptr already exist (and also > will avoid ENOMEM for such cases). Sure thing. Will post an updated version soon. Thanks. -- tejun -- 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/