From: Boaz Harrosh <bharrosh@panasas.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: James.Bottomley@HansenPartnership.com, jens.axboe@oracle.com,
linux-scsi@vger.kernel.org
Subject: Re: [RFD] blk_rq_map_pages new API
Date: Thu, 12 Feb 2009 11:19:09 +0200 [thread overview]
Message-ID: <4993E98D.8020001@panasas.com> (raw)
In-Reply-To: <4993DD9A.6070701@panasas.com>
Boaz Harrosh wrote:
> /**
> * blk_rq_map_pages - Receives an array of pages and appends them to a request structure
> *
> * @rq: The request to map
> * @pages_info: A structure that specifies the array of pages, offset and more that need to be
> * map to the request. the @pages_info->null_mapped is assumed to be 1 and is ignored.
> * @length: Total bytes to map. Array of pages can be larger, stop mapping after @length bytes mapped.
> * @max_pages: When allocating the internal bio use @max_pages as an hint that says the amount of anticipated
> * pages that will be mapped. This member is optional and can be zero.
> *
> * blk_rq_map_pages can be called multiple times so the user does not need to allocate a contiguous array
> * of struct page pointers but can call this routine multiple times. In that case max_pages can be set
> * so no bio re-allocation occurs.
> * There is no unmap function for this mapping, the request is completed in the regular way.
> */
>
> int blk_rq_map_pages(struct request rq, struct *rq_map_data pages_info, unsigned length, unsigned max_pages);
>
>
> Implementation comments:
> - Then when this member is available many places that call blk_rq_map_user() rq_map_data and null_mapped set,
> and buff == NULL, can be converted to this member.
>
> - Internal block implementation is refactored to not duplicate any code with blk_rq_map_user().
>
> Thanks for any comments
> Boaz
>
> --
FUJITA Tomonori wrote:
> Please send a patch to implement the proposal.
>
Is the above API accepted by you? Is it accepted by Jens?
Should I also attempt first comment above.
If its OK I will implement it ASAP.
Thanks
Boaz
next prev parent reply other threads:[~2009-02-12 9:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 16:23 [PATCH 0/3] remove scsi_req_map_sg FUJITA Tomonori
2008-12-13 16:23 ` [PATCH 1/3] " FUJITA Tomonori
2008-12-13 16:23 ` [PATCH 2/3] block: unexport blk_rq_append_bio FUJITA Tomonori
2008-12-13 16:23 ` [PATCH 3/3] block: unexport bio_add_pc_page FUJITA Tomonori
2009-02-10 17:43 ` [PATCH 2/3] block: unexport blk_rq_append_bio James Bottomley
2009-02-10 18:19 ` James Bottomley
2009-02-11 0:21 ` FUJITA Tomonori
2009-02-11 8:17 ` Boaz Harrosh
2009-02-11 8:19 ` Boaz Harrosh
2009-02-11 9:15 ` Boaz Harrosh
2009-02-11 14:32 ` FUJITA Tomonori
2009-02-11 14:52 ` Boaz Harrosh
2009-02-11 15:01 ` FUJITA Tomonori
2009-02-11 15:07 ` Boaz Harrosh
2009-02-11 15:21 ` FUJITA Tomonori
2009-02-11 15:41 ` Boaz Harrosh
2009-02-11 16:04 ` FUJITA Tomonori
2009-02-11 16:30 ` James Bottomley
2009-02-11 17:55 ` Boaz Harrosh
2009-02-12 1:30 ` FUJITA Tomonori
2009-02-12 8:24 ` Boaz Harrosh
2009-02-12 8:28 ` [RFD] blk_rq_map_pages new API Boaz Harrosh
2009-02-12 9:19 ` Boaz Harrosh [this message]
2009-02-12 9:50 ` FUJITA Tomonori
2009-02-12 10:20 ` FUJITA Tomonori
2009-02-12 11:34 ` Boaz Harrosh
2009-02-12 8:41 ` [PATCH 2/3] block: unexport blk_rq_append_bio FUJITA Tomonori
2009-02-12 9:14 ` Boaz Harrosh
2009-02-12 9:50 ` FUJITA Tomonori
2009-02-12 12:19 ` [PATCH] [RFC] block: Don't let blk_put_request leak BIOs Boaz Harrosh
2009-02-12 13:49 ` Boaz Harrosh
2009-02-12 13:56 ` Boaz Harrosh
2009-02-12 17:27 ` [PATCH 1/2] " Boaz Harrosh
2009-02-12 17:30 ` [PATCH 2/2] [RFC] libosd: Don't let osd abuse block internals, now that it's fixed Boaz Harrosh
2009-02-12 14:48 ` [PATCH 2/3] block: unexport blk_rq_append_bio James Bottomley
2009-02-12 16:51 ` Boaz Harrosh
2008-12-15 7:28 ` [PATCH 0/3] remove scsi_req_map_sg Jens Axboe
2008-12-18 8:14 ` FUJITA Tomonori
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=4993E98D.8020001@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@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 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).