From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ming Lei <ming.lei@redhat.com>, linux-block@vger.kernel.org
Subject: avoid calling nth_page in the block I/O path
Date: Mon, 8 Apr 2019 12:46:36 +0200 [thread overview]
Message-ID: <20190408104641.4905-1-hch@lst.de> (raw)
Hi Jens,
you complained about the overhead of calling nth_page in the multipage
bio_vec enabled I/O path a while ago. While I can't really reproduce
the numbers on my (slower) hardware we could avoid the nth_page calls
pretty easily with a few tweaks. Can you take a look at this series?
next reply other threads:[~2019-04-08 10:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 10:46 Christoph Hellwig [this message]
2019-04-08 10:46 ` [PATCH 1/5] block: rewrite blk_bvec_map_sg to avoid a nth_page call Christoph Hellwig
2019-04-08 14:03 ` Johannes Thumshirn
2019-04-08 22:04 ` Bart Van Assche
2019-04-08 22:51 ` Ming Lei
2019-04-15 19:44 ` Guenter Roeck
2019-04-15 20:52 ` Christoph Hellwig
2019-04-15 21:07 ` Guenter Roeck
2019-04-16 6:33 ` Christoph Hellwig
2019-04-16 14:09 ` Guenter Roeck
2019-04-16 17:08 ` Guenter Roeck
2019-04-16 17:10 ` Christoph Hellwig
2019-04-16 17:51 ` Guenter Roeck
2019-04-17 5:27 ` Christoph Hellwig
2019-04-17 13:42 ` Guenter Roeck
2019-04-17 21:59 ` Guenter Roeck
2019-04-19 2:27 ` Ming Lei
2019-04-19 2:36 ` Ming Lei
2019-04-08 10:46 ` [PATCH 2/5] block: refactor __bio_iov_bvec_add_pages Christoph Hellwig
2019-04-08 11:07 ` Johannes Thumshirn
2019-04-08 22:06 ` Bart Van Assche
2019-04-08 10:46 ` [PATCH 3/5] block: don't allow multiple bio_iov_iter_get_pages calls per bio Christoph Hellwig
2019-04-08 11:13 ` Johannes Thumshirn
2019-04-08 22:17 ` Bart Van Assche
2019-04-09 10:05 ` Christoph Hellwig
2019-04-08 10:46 ` [PATCH 4/5] block: change how we get page references in bio_iov_iter_get_pages Christoph Hellwig
2019-04-08 10:46 ` [PATCH 5/5] block: only allow contiguous page structs in a bio_vec Christoph Hellwig
2019-04-09 16:15 ` avoid calling nth_page in the block I/O path Jens Axboe
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=20190408104641.4905-1-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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 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.