linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: <koverstreet@google.com>
Cc: <linux-bcache@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<dm-devel@redhat.com>, <linux-fsdevel@vger.kernel.org>,
	<tj@kernel.org>, <axboe@kernel.dk>, <agk@redhat.com>,
	<neilb@suse.de>
Subject: Re: [PATCH 09/13] block: Add an explicit bio flag for bios that own their bvec
Date: Fri, 18 May 2012 20:07:40 +0300	[thread overview]
Message-ID: <4FB681DC.7000700@panasas.com> (raw)
In-Reply-To: <363875943e9d0e13bee6ed28239280543e6e5055.1337308722.git.koverstreet@google.com>

On 05/18/2012 05:59 AM, koverstreet@google.com wrote:

> From: Kent Overstreet <koverstreet@google.com>
> 
> This is for the new bio splitting code. When we split a bio, if the
> split occured on a bvec boundry we reuse the bvec for the new bio. But
> that means bio_free() can't free it, hence the explicit flag.
> 
> Signed-off-by: Kent Overstreet <koverstreet@google.com>
> ---
>  fs/bio.c                  |    3 ++-
>  include/linux/blk_types.h |    1 +
>  2 files changed, 3 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/bio.c b/fs/bio.c
> index ecc9088..3332800 100644
> --- a/fs/bio.c
> +++ b/fs/bio.c
> @@ -234,7 +234,7 @@ void bio_free(struct bio *bio, struct bio_set *bs)
>  {
>  	void *p;
>  
> -	if (bio_has_allocated_vec(bio))
> +	if (bio_flagged(bio, BIO_HAS_VEC))
>  		bvec_free_bs(bs, bio->bi_io_vec, BIO_POOL_IDX(bio));
>  
>  	if (bio_integrity(bio))
> @@ -305,6 +305,7 @@ struct bio *bio_alloc_bioset(gfp_t gfp_mask, int nr_iovecs, struct bio_set *bs)
>  			goto err_free;
>  
>  		nr_iovecs = bvec_nr_vecs(idx);
> +		bio->bi_flags |= 1 << BIO_HAS_VEC;
>  	}
>  out_set:
>  	bio->bi_flags |= idx << BIO_POOL_OFFSET;
> diff --git a/include/linux/blk_types.h b/include/linux/blk_types.h
> index bd9a610..10fca21 100644
> --- a/include/linux/blk_types.h
> +++ b/include/linux/blk_types.h
> @@ -101,6 +101,7 @@ struct bio {
>  #define BIO_FS_INTEGRITY 9	/* fs owns integrity data, not block layer */
>  #define BIO_QUIET	10	/* Make BIO Quiet */
>  #define BIO_MAPPED_INTEGRITY 11/* integrity metadata has been remapped */
> +#define BIO_HAS_VEC	12	/* bio_free() should free bvec */


Just an English nit
BIO with out any VECs is when bi_max_vecs is zero. Id prefer a name that
denotes allocation or ownership.
BIO_OWN_VEC or BIO_ALLOC_VEC or BIO_DELETE_VEC

And one technical problem.

I would prefer to negate this bit. Zero is the default, set on
the exception. Safer and also more logical.

 BIO_NO_DELETE_VEC

>  #define bio_flagged(bio, flag)	((bio)->bi_flags & (1 << (flag)))
>  
>  /*



Thanks
Boaz

  parent reply	other threads:[~2012-05-18 17:08 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18  2:59 [PATCH 00/13] Block cleanups (for bcache) koverstreet
2012-05-18  2:59 ` [PATCH 01/13] block: Generalized bio pool freeing koverstreet
2012-05-18 15:55   ` Tejun Heo
2012-05-18 16:14     ` [dm-devel] " Alasdair G Kergon
2012-05-18  2:59 ` [PATCH 02/13] dm: kill dm_rq_bio_destructor koverstreet
2012-05-18 15:57   ` Tejun Heo
2012-05-18 16:43     ` [dm-devel] " Alasdair G Kergon
2012-05-18 18:50       ` Kent Overstreet
2012-05-22  4:29         ` Jun'ichi Nomura
2012-05-18  2:59 ` [PATCH 03/13] block: Add bio_clone_bioset() koverstreet
2012-05-18 16:05   ` Tejun Heo
2012-05-18 20:31     ` Kent Overstreet
2012-05-18 16:11   ` [dm-devel] " Vivek Goyal
2012-05-18 18:55     ` Kent Overstreet
2012-05-18  2:59 ` [PATCH 04/13] block: Add bio_clone_kmalloc() koverstreet
2012-05-18 16:09   ` Tejun Heo
2012-05-18 20:39     ` Kent Overstreet
2012-05-18 16:45   ` Boaz Harrosh
2012-05-18  2:59 ` [PATCH 05/13] block: Only clone bio vecs that are in use koverstreet
2012-05-18 16:13   ` Tejun Heo
2012-05-18 21:14     ` Kent Overstreet
2012-05-18  2:59 ` [PATCH 06/13] block: Add bio_reset() koverstreet
2012-05-18 16:16   ` Tejun Heo
2012-05-18 21:48     ` Kent Overstreet
2012-05-18  2:59 ` [PATCH 07/13] pktcdvd: Switch to bio_kmalloc() koverstreet
2012-05-18 16:18   ` Tejun Heo
2012-05-18  2:59 ` [PATCH 08/13] block: Kill bi_destructor koverstreet
2012-05-18 16:21   ` Tejun Heo
2012-05-18 22:21     ` Kent Overstreet
2012-05-18  2:59 ` [PATCH 09/13] block: Add an explicit bio flag for bios that own their bvec koverstreet
2012-05-18 16:30   ` Tejun Heo
2012-05-18 21:49     ` Kent Overstreet
2012-05-18 17:07   ` Boaz Harrosh [this message]
2012-05-18  2:59 ` [PATCH 10/13] block: Rework bio splitting koverstreet
2012-05-18 17:07   ` Tejun Heo
2012-05-18 17:46   ` Boaz Harrosh
2012-05-18  2:59 ` [PATCH 11/13] Closures koverstreet
2012-05-18 17:08   ` Tejun Heo
2012-05-18  2:59 ` [PATCH 12/13] Make generic_make_request handle arbitrarily large bios koverstreet
2012-05-18  8:05   ` NeilBrown
2012-05-18  8:14     ` Kent Overstreet
2012-05-21 17:17       ` [dm-devel] " Vivek Goyal
2012-05-21 17:55         ` Kent Overstreet
2012-05-21 18:32           ` Vivek Goyal
2012-05-18 17:52   ` Tejun Heo
2012-05-19  0:59     ` [dm-devel] " Alasdair G Kergon
2012-05-18 22:48   ` Mikulas Patocka
2012-05-18  3:00 ` [PATCH 13/13] Gut bio_add_page() koverstreet

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=4FB681DC.7000700@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=agk@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=koverstreet@google.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=tj@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).