Linux Device Mapper development
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Junichi Nomura <j-nomura@ce.jp.nec.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	device-mapper development <dm-devel@redhat.com>,
	Kent Overstreet <kmo@daterainc.com>
Subject: Re: [PATCH 3/4] block: add bioset_nobvec_create()
Date: Fri, 3 Oct 2014 09:16:05 -0400	[thread overview]
Message-ID: <20141003131605.GA11977@redhat.com> (raw)
In-Reply-To: <542E8EAB.5010603@ce.jp.nec.com>

On Fri, Oct 03 2014 at  7:55am -0400,
Junichi Nomura <j-nomura@ce.jp.nec.com> wrote:

> Users of bio_clone_fast() do not need its own bvecs.
> Allocating bvec mempool for such users is waste of memory.
> 
> This variant allows them to create bioset without bvec mempool.
> 
> Signed-off-by: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
> ---
>  block/bio.c         | 61 ++++++++++++++++++++++++++++++++++++++---------------
>  include/linux/bio.h |  1 +
>  2 files changed, 45 insertions(+), 17 deletions(-)
> 
> diff --git a/block/bio.c b/block/bio.c
> index 3e6331d..98c5100 100644
> --- a/block/bio.c
> +++ b/block/bio.c
> @@ -1900,20 +1903,9 @@ void bioset_free(struct bio_set *bs)
>  }
>  EXPORT_SYMBOL(bioset_free);
>  
> -/**
> - * bioset_create  - Create a bio_set
> - * @pool_size:	Number of bio and bio_vecs to cache in the mempool
> - * @front_pad:	Number of bytes to allocate in front of the returned bio
> - *
> - * Description:
> - *    Set up a bio_set to be used with @bio_alloc_bioset. Allows the caller
> - *    to ask for a number of bytes to be allocated in front of the bio.
> - *    Front pad allocation is useful for embedding the bio inside
> - *    another structure, to avoid allocating extra data to go with the bio.
> - *    Note that the bio must be embedded at the END of that structure always,
> - *    or things will break badly.
> - */
> -struct bio_set *bioset_create(unsigned int pool_size, unsigned int front_pad)
> +static struct bio_set *__bioset_create(unsigned int pool_size,
> +				       unsigned int front_pad,
> +				       unsigned int create_bvec_pool)
>  {
>  	unsigned int back_pad = BIO_INLINE_VECS * sizeof(struct bio_vec);
>  	struct bio_set *bs;

Any reason not to use bool for create_bvec_pool?

> @@ -1951,8 +1945,41 @@ bad:
>  	bioset_free(bs);
>  	return NULL;
>  }
> +
> +/**
> + * bioset_create  - Create a bio_set
> + * @pool_size:	Number of bio and bio_vecs to cache in the mempool
> + * @front_pad:	Number of bytes to allocate in front of the returned bio
> + *
> + * Description:
> + *    Set up a bio_set to be used with @bio_alloc_bioset. Allows the caller
> + *    to ask for a number of bytes to be allocated in front of the bio.
> + *    Front pad allocation is useful for embedding the bio inside
> + *    another structure, to avoid allocating extra data to go with the bio.
> + *    Note that the bio must be embedded at the END of that structure always,
> + *    or things will break badly.
> + */
> +struct bio_set *bioset_create(unsigned int pool_size, unsigned int front_pad)
> +{
> +	return __bioset_create(pool_size, front_pad, 1);
> +}
>  EXPORT_SYMBOL(bioset_create);
>  
> +/**
> + * bioset_nobvec_create  - Create a bio_set without bio_vec mempool
> + * @pool_size:	Number of bio to cache in the mempool
> + * @front_pad:	Number of bytes to allocate in front of the returned bio
> + *
> + * Description:
> + *    Same functionality as bioset_create() except that mempool is not
> + *    created for bio_vecs. Saving some memory for bio_clone_fast() users.
> + */
> +struct bio_set *bioset_nobvec_create(unsigned int pool_size, unsigned int front_pad)
> +{
> +	return __bioset_create(pool_size, front_pad, 0);
> +}
> +EXPORT_SYMBOL(bioset_nobvec_create);
> +
>  #ifdef CONFIG_BLK_CGROUP
>  /**
>   * bio_associate_current - associate a bio with %current

And use true and false accordingly...

> diff --git a/include/linux/bio.h b/include/linux/bio.h
> index b39e500..7d7b2a7 100644
> --- a/include/linux/bio.h
> +++ b/include/linux/bio.h
> @@ -342,6 +342,7 @@ static inline struct bio *bio_next_split(struct bio *bio, int sectors,
>  }
>  
>  extern struct bio_set *bioset_create(unsigned int, unsigned int);
> +extern struct bio_set *bioset_nobvec_create(unsigned int, unsigned int);
>  extern void bioset_free(struct bio_set *);
>  extern mempool_t *biovec_create_pool(int pool_entries);

Also, I prefer the function name: bioset_create_nobvec (to keep it in
the "bioset_create" family).

Otherwise, please feel free to add to v2:

Acked-by: Mike Snitzer <snitzer@redhat.com>

  reply	other threads:[~2014-10-03 13:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03 11:48 [PATCH 0/4] dm: reduce memory overhead of DM devices Junichi Nomura
2014-10-03 11:55 ` [PATCH 1/4] dm: remove nr_iovecs parameter from alloc_tio() Junichi Nomura
2014-10-03 20:01   ` Mike Snitzer
2014-10-03 11:55 ` [PATCH 2/4] block: use bio_clone_fast() in blk_rq_prep_clone() Junichi Nomura
2014-10-03 11:55 ` [PATCH 3/4] block: add bioset_nobvec_create() Junichi Nomura
2014-10-03 13:16   ` Mike Snitzer [this message]
2014-10-03 11:55 ` [PATCH 4/4] dm: use bioset_nobvec_create() Junichi Nomura
2014-10-03 13:23 ` [PATCH 0/4] dm: reduce memory overhead of DM devices Mike Snitzer
2014-10-03 20:48   ` Mike Snitzer
2014-10-03 20:57     ` Jens Axboe
2014-10-03 21:04       ` Mike Snitzer
2014-10-03 21:27     ` [PATCH v2 1/4] dm: remove nr_iovecs parameter from alloc_tio() Mike Snitzer
2014-10-03 21:27     ` [PATCH v2 2/4] block: use bio_clone_fast() in blk_rq_prep_clone() Mike Snitzer
2014-10-03 21:27     ` [PATCH v2 3/4] block: add bioset_create_nobvec() Mike Snitzer
2014-10-03 21:27     ` [PATCH v2 4/4] dm: use bioset_create_nobvec() Mike Snitzer
2014-10-05 23:06       ` Junichi Nomura
2014-10-06  0:24         ` Mike Snitzer
2014-10-04 17:01 ` [PATCH 0/4] dm: reduce memory overhead of DM devices Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141003131605.GA11977@redhat.com \
    --to=snitzer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=j-nomura@ce.jp.nec.com \
    --cc=kmo@daterainc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox