All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Chris Mason <clm@meta.com>
Cc: Christoph Hellwig <hch@lst.de>, Chris Mason <clm@fb.com>,
	linux-btrfs@vger.kernel.org, dsterba@suse.com,
	josef@toxicpanda.com
Subject: Re: [PATCH RFC] Btrfs: only subtract from len_to_oe_boundary when it is tracking an extent
Date: Mon, 31 Jul 2023 21:35:43 +0200	[thread overview]
Message-ID: <20230731193543.GA13557@lst.de> (raw)
In-Reply-To: <35b14d0e-3a53-fca7-8290-b26f31d07fb5@meta.com>

On Mon, Jul 31, 2023 at 02:52:23PM -0400, Chris Mason wrote:
> > I'm torn.  On the one hand "btrfs: limit write bios to a single ordered
> > extent" is a pretty significant behavior change, on the other hand
> > stable-only patches with totally different behavior are always a bit
> > strange.
> 
> When are we creating bios without bio_ctrl->wbc set?  I think reads will
> do this?

Yes.  These days the bio_ctrl is only used for data I/O, and
bio_ctrl->wbc is set for all writeback I/O, and clear for all read I/O.

  reply	other threads:[~2023-07-31 19:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-30 19:02 [PATCH RFC] Btrfs: only subtract from len_to_oe_boundary when it is tracking an extent Chris Mason
2023-07-30 20:27 ` Sweet Tea Dorminy
2023-07-31 19:22   ` Chris Mason
2023-08-01  2:59     ` Sweet Tea Dorminy
2023-07-31  2:27 ` Qu Wenruo
2023-07-31  7:02   ` Christoph Hellwig
2023-07-31 18:10     ` Chris Mason
2023-08-01  0:58       ` Qu Wenruo
2023-07-31  7:00 ` Christoph Hellwig
2023-07-31 18:52   ` Chris Mason
2023-07-31 19:35     ` Christoph Hellwig [this message]
2023-07-31 21:05       ` Chris Mason

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=20230731193543.GA13557@lst.de \
    --to=hch@lst.de \
    --cc=clm@fb.com \
    --cc=clm@meta.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@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.