From: "H. Peter Anvin" <hpa@zytor.com>
To: Chris Mason <clm@fb.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Formalizing the use of Boot Area B
Date: Tue, 20 May 2014 17:04:49 -0700 [thread overview]
Message-ID: <537BEDA1.2010900@zytor.com> (raw)
In-Reply-To: <537BE73F.7040307@fb.com>
On 05/20/2014 04:37 PM, Chris Mason wrote:
>
> Hi Peter,
>
> We do leave the first 1MB of each device alone. Can we do 256K-1024K
> for the boot loader? We don't have an immediate need for the extra
> space, but I'd like to reserve a little more than the extra 64KB.
>
Incidentally, the current version of mkfs.btrfs actually leaves not
1 MB (1024K) but rather 1104K (64K+16K+1024K). Not sure if that is
intentional.
-hpa
prev parent reply other threads:[~2014-05-21 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 0:01 Formalizing the use of Boot Area B H. Peter Anvin
2014-05-20 23:29 ` H. Peter Anvin
2014-05-20 23:37 ` Chris Mason
2014-05-20 23:39 ` H. Peter Anvin
2014-05-21 0:04 ` H. Peter Anvin [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=537BEDA1.2010900@zytor.com \
--to=hpa@zytor.com \
--cc=clm@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;
as well as URLs for NNTP newsgroup(s).