Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757062Ab2HVVaW (ORCPT ); Wed, 22 Aug 2012 17:30:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49577 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753933Ab2HVVaT (ORCPT ); Wed, 22 Aug 2012 17:30:19 -0400 Date: Wed, 22 Aug 2012 17:30:10 -0400 From: Vivek Goyal To: Kent Overstreet Cc: linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org, dm-devel@redhat.com, tj@kernel.org, mpatocka@redhat.com, bharrosh@panasas.com, Alasdair Kergon Subject: Re: [PATCH v6 02/13] dm: Use bioset's front_pad for dm_rq_clone_bio_info Message-ID: <20120822213010.GA8020@redhat.com> References: <1345655050-28199-1-git-send-email-koverstreet@google.com> <1345655050-28199-3-git-send-email-koverstreet@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1345655050-28199-3-git-send-email-koverstreet@google.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2066 Lines: 63 On Wed, Aug 22, 2012 at 10:03:59AM -0700, Kent Overstreet wrote: > Previously, dm_rq_clone_bio_info needed to be freed by the bio's > destructor to avoid a memory leak in the blk_rq_prep_clone() error path. > This gets rid of a memory allocation and means we can kill > dm_rq_bio_destructor. > > v6: Fix comment on struct dm_rq_clone_bio_info, per Tejun > > Signed-off-by: Kent Overstreet > CC: Alasdair Kergon > --- > drivers/md/dm.c | 39 +++++++++++---------------------------- > 1 file changed, 11 insertions(+), 28 deletions(-) > > diff --git a/drivers/md/dm.c b/drivers/md/dm.c > index 0c3d6dd..5ed9779 100644 > --- a/drivers/md/dm.c > +++ b/drivers/md/dm.c > @@ -86,12 +86,17 @@ struct dm_rq_target_io { > }; > > /* > - * For request-based dm. > - * One of these is allocated per bio. > + * For request-based dm - the bio clones we allocate are embedded in these > + * structs. > + * > + * We allocate these with bio_alloc_bioset, using the front_pad parameter when > + * the bioset is created - this means the bio has to come at the end of the > + * struct. > */ > struct dm_rq_clone_bio_info { > struct bio *orig; > struct dm_rq_target_io *tio; > + struct bio clone; > }; > > union map_info *dm_get_mapinfo(struct bio *bio) > @@ -467,16 +472,6 @@ static void free_rq_tio(struct dm_rq_target_io *tio) > mempool_free(tio, tio->md->tio_pool); > } > > -static struct dm_rq_clone_bio_info *alloc_bio_info(struct mapped_device *md) > -{ > - return mempool_alloc(md->io_pool, GFP_ATOMIC); > -} > - > -static void free_bio_info(struct dm_rq_clone_bio_info *info) > -{ > - mempool_free(info, info->tio->md->io_pool); > -} > - With this change, do you still need "_rq_bio_info_cache" slab cache? I would think that it can be cleaned up now? Thanks Vivek -- 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/