From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 0/3][v2] Add comments describing how space reservation works
Date: Wed, 5 Feb 2020 14:32:52 +0100 [thread overview]
Message-ID: <20200205133251.GJ2654@twin.jikos.cz> (raw)
In-Reply-To: <20200204181856.765916-1-josef@toxicpanda.com>
On Tue, Feb 04, 2020 at 01:18:53PM -0500, Josef Bacik wrote:
> v1->v2:
> - Fixed spelling mistakes, discovered you can use ':set spell' for files other
> than git commit messages.
> - Reworked some of the explanations to be more visual to describe the general
> flow.
>
> --------------- Original email ------------------
> In talking with Nikolay about the data reservation patches it became clear that
> there's way more about the space reservation system that exists soley in my head
> than I thought. I've written three big comments on the different sections of
> the space reservation system to hopefully help people understand how the system
> works generally. Again this is from my point of view, and since I'm the one who
> wrote it I'm not sure where the gaps in peoples understanding is, so if there's
> something that is not clear here now is the time to bring it up. Hopefully this
> will make reviewing patches I submit to this system less scary for reviewers.
> Thanks,
>
Thanks, added to misc-next.
prev parent reply other threads:[~2020-02-05 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 18:18 [PATCH 0/3][v2] Add comments describing how space reservation works Josef Bacik
2020-02-04 18:18 ` [PATCH 1/3] btrfs: add a comment describing block-rsvs Josef Bacik
2020-02-07 15:11 ` David Sterba
2020-02-04 18:18 ` [PATCH 2/3] btrfs: add a comment describing delalloc space reservation Josef Bacik
2020-02-04 18:18 ` [PATCH 3/3] btrfs: describe the space reservation system in general Josef Bacik
2020-02-05 13:32 ` David Sterba [this message]
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=20200205133251.GJ2654@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox