From: Jordan Justen <jordan.l.justen@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Gary Ching-Pang Lin <glin@suse.com>
Subject: Re: [PATCH 2/3] OvmfPkg: introduce FD_SIZE_4MB (mainly) for Windows HCK
Date: Mon, 01 May 2017 10:15:46 -0700 [thread overview]
Message-ID: <149365894632.25909.11739243410891079091@jljusten-skl> (raw)
In-Reply-To: <c010a543-1d66-05f1-a441-59e2c06c98c6@redhat.com>
On 2017-05-01 03:51:42, Laszlo Ersek wrote:
> On 04/30/17 23:16, Jordan Justen wrote:
> > What are the chances
> > that 248k will cover it? Unfortunately (or fortunately), no one I've
> > asked seem to know of any plans for the requirement to increase beyond
> > 120k.
>
> Again, I agree this is a valid concern; there's no way to guarantee
> 248KB will be enough for 7 years (I keep saying 7 years, that's
> important to me, others might care about a different time frame).
>
> Given that 120-128KB has gone from "generous" to "required" in 2.5
> years, I feel that providing 248KB for the next 7 years (thereby more
> than quadrupling OVMF's current offer) is the low water mark for "prudent".
Since we are trying to predict the future, I don't think we should
stop just shy of a power-of-two. I don't know where the 120k number
comes from, but I don't think we should bet on the next power-of-two
minus 8k.
Regarding the event log, it has been ignored in OVMF, but I'd like to
ask around a bit to see if it could be useful to have more than 4k.
> If you'd like us to go, say, 504KB live varstore, 1MB NV, and 5MB or 6MB
> total, I'm game.
Uh, no. I'd rather go with 128k, and I'd also rather stay with 2MB. :)
-Jordan
next prev parent reply other threads:[~2017-05-01 17:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 20:14 [PATCH 0/3] OvmfPkg: add FD_SIZE_4MB for Windows HCK SB tests, and for future proofing Laszlo Ersek
2017-04-29 20:14 ` [PATCH 1/3] OvmfPkg/OvmfPkg.fdf.inc: extract VARS_LIVE_SIZE and VARS_SPARE_SIZE macros Laszlo Ersek
2017-04-29 20:14 ` [PATCH 2/3] OvmfPkg: introduce FD_SIZE_4MB (mainly) for Windows HCK Laszlo Ersek
2017-04-30 0:48 ` Jordan Justen
2017-04-30 14:42 ` Laszlo Ersek
2017-04-30 21:16 ` Jordan Justen
2017-05-01 10:51 ` Laszlo Ersek
2017-05-01 17:15 ` Jordan Justen [this message]
2017-05-01 17:23 ` Jordan Justen
2017-05-01 18:40 ` Laszlo Ersek
2017-05-01 19:20 ` Jordan Justen
2017-05-01 23:07 ` Laszlo Ersek
2017-05-01 23:38 ` Jordan Justen
2017-05-02 14:39 ` Laszlo Ersek
2017-05-02 18:22 ` Jordan Justen
2017-05-02 19:31 ` Laszlo Ersek
2017-05-02 21:45 ` Jordan Justen
2017-05-03 13:46 ` Laszlo Ersek
2017-05-01 0:06 ` Laszlo Ersek
2017-04-29 20:15 ` [PATCH 3/3] OvmfPkg: raise max variable size (auth & non-auth) to 33KB for FD_SIZE_4MB Laszlo Ersek
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-list 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=149365894632.25909.11739243410891079091@jljusten-skl \
--to=devel@edk2.groups.io \
/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