From: Sagi Grimberg <sagig@dev.mellanox.co.il>
To: Ming Lei <ming.lei@canonical.com>, Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org
Cc: linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/4] block: bio: introduce helpers to get the 1st and last bvec
Date: Mon, 15 Feb 2016 10:19:49 +0200 [thread overview]
Message-ID: <56C18A25.50803@dev.mellanox.co.il> (raw)
In-Reply-To: <1455519687-23873-2-git-send-email-ming.lei@canonical.com>
> +/*
> + * bio_get_last_bvec() is introduced to get the last bvec of one
> + * bio for bio_will_gap().
> + *
> + * TODO: make it more efficient.
> + */
> +static inline void bio_get_last_bvec(struct bio *bio, struct bio_vec *bv)
> +{
> + struct bvec_iter iter;
> +
> + bio_for_each_segment(*bv, bio, iter)
> + if (bv->bv_len == iter.bi_size)
> + break;
> +}
This helper is used for each req/bio once or more. I'd say
it's critical to make it efficient and not settle for
a quick bail for drivers that don't have a virt_boundary
like you did in patch #2.
However, given that it's a regression bug fix I'm not sure it's the best
idea to add logic here.
next prev parent reply other threads:[~2016-02-15 8:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 7:01 [PATCH 0/4] block: fix bio_will_gap() Ming Lei
2016-02-15 7:01 ` [PATCH 1/4] block: bio: introduce helpers to get the 1st and last bvec Ming Lei
2016-02-15 8:19 ` Sagi Grimberg [this message]
2016-02-15 9:42 ` Ming Lei
2016-02-15 20:06 ` Sagi Grimberg
2016-02-16 13:03 ` Ming Lei
2016-02-17 3:08 ` Elliott, Robert (Persistent Memory)
2016-02-18 4:24 ` Kent Overstreet
2016-02-18 6:16 ` Ming Lei
2016-02-19 1:47 ` Ming Lei
2016-02-15 7:01 ` [PATCH 2/4] block: check virt boundary in bio_will_gap() Ming Lei
2016-02-15 8:22 ` Sagi Grimberg
2016-02-15 10:27 ` Ming Lei
2016-02-15 20:27 ` Sagi Grimberg
2016-02-16 13:05 ` Ming Lei
2016-02-16 13:08 ` Ming Lei
2016-02-15 8:33 ` [PATCH 0/4] block: fix bio_will_gap() Sagi Grimberg
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=56C18A25.50803@dev.mellanox.co.il \
--to=sagig@dev.mellanox.co.il \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.