mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Peter Osterlund <petero2@telia.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: ext2 on a CD-RW
Date: Fri, 2 Jan 2004 14:59:21 +0100	[thread overview]
Message-ID: <20040102135921.GB20572@suse.de> (raw)
In-Reply-To: <m2vfnu79n8.fsf@telia.com>

On Fri, Jan 02 2004, Peter Osterlund wrote:
> Jens Axboe <axboe@suse.de> writes:
> 
> > I just looked but could not find anything about it, there's been some
> > talk on this list. But it doesn't look like it ever got documented in
> > text writing. That needs to be fixed for sure, thanks for the patch. It
> > probably wants documenting in fs/bio.c:bio_add_page() too.
> 
> OK, here is an updated patch.
> 
> Improved documentation for blk_queue_merge_bvec() and bio_add_page().
> 
> 
>  linux-petero/drivers/block/ll_rw_blk.c |    8 +++++---
>  linux-petero/fs/bio.c                  |    4 +++-
>  2 files changed, 8 insertions(+), 4 deletions(-)
> 
> diff -puN drivers/block/ll_rw_blk.c~block-api-doc drivers/block/ll_rw_blk.c
> --- linux/drivers/block/ll_rw_blk.c~block-api-doc	2004-01-02 13:54:38.000000000 +0100
> +++ linux-petero/drivers/block/ll_rw_blk.c	2004-01-02 13:55:50.000000000 +0100
> @@ -173,9 +173,11 @@ EXPORT_SYMBOL(blk_queue_prep_rq);
>   * are dynamic, and thus we have to query the queue whether it is ok to
>   * add a new bio_vec to a bio at a given offset or not. If the block device
>   * has such limitations, it needs to register a merge_bvec_fn to control
> - * the size of bio's sent to it. Per default now merge_bvec_fn is defined for
> - * a queue, and only the fixed limits are honored.
> - *
> + * the size of bio's sent to it. Note that a block device *must* allow a
> + * single page to be added to an empty bio. The block device driver may want
> + * to use the bio_split() function to deal with these bio's. Per default
> + * no merge_bvec_fn is defined for a queue, and only the fixed limits are
> + * honored.
>   */
>  void blk_queue_merge_bvec(request_queue_t *q, merge_bvec_fn *mbfn)
>  {
> diff -puN fs/bio.c~block-api-doc fs/bio.c
> --- linux/fs/bio.c~block-api-doc	2004-01-02 14:00:13.000000000 +0100
> +++ linux-petero/fs/bio.c	2004-01-02 14:37:41.000000000 +0100
> @@ -290,7 +290,9 @@ int bio_get_nr_vecs(struct block_device 
>   *
>   *	Attempt to add a page to the bio_vec maplist. This can fail for a
>   *	number of reasons, such as the bio being full or target block
> - *	device limitations.
> + *	device limitations. The target block device must not disallow bio's

That may not be unparsable, but I'll remove the double negative :).
Otherwise comitted, thanks.

-- 
Jens Axboe


  reply	other threads:[~2004-01-02 14:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-01 23:47 Peter Osterlund
2004-01-02  0:24 ` Andrew Morton
2004-01-02  1:30   ` Peter Osterlund
2004-01-02  9:06     ` Arjan van de Ven
2004-01-02 10:09       ` Jens Axboe
2004-01-02 10:51       ` Peter Osterlund
2004-01-02 10:59         ` Jens Axboe
2004-01-02 12:09           ` Peter Osterlund
2004-01-02 12:19             ` Jens Axboe
2004-01-02 13:38               ` Peter Osterlund
2004-01-02 13:59                 ` Jens Axboe [this message]
2004-01-02 16:12           ` Peter Osterlund
2004-03-29 15:38           ` Peter Osterlund
2004-01-02 10:08     ` Jens Axboe
2004-01-03 19:14 ` Pavel Machek
2004-01-03 20:32   ` Peter Osterlund

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=20040102135921.GB20572@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.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

Powered by JetHome