From: John Snow <jsnow@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: kwolf@redhat.com, ehabkost@redhat.com, qemu-devel@nongnu.org,
wainersm@redhat.com, Markus Armbruster <armbru@redhat.com>,
"Niteesh G. S." <niteesh.gs@gmail.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: GSoC Intro - TUI interface for QMP
Date: Thu, 10 Jun 2021 10:35:25 -0400 [thread overview]
Message-ID: <bb073532-6d90-4a3d-80a0-93bfad45b10d@redhat.com> (raw)
In-Reply-To: <YMCvDpooagPkPN2H@redhat.com>
On 6/9/21 8:07 AM, Daniel P. Berrangé wrote:
> I think that's overthinking things. Even a small QEMU install is
> 10s of MB in size once you add up the qemu binary, firmware blobs
> and depedancies. If we only keep the raw help text from the json,
> we'll have < 1/2 MB, which is lost in the noise of the overall
> deploymnt size. No need for compression or complex load-on-demand,
> just keep it small and simple.
>
Yes, you're right. Our first step should be to keep it small and simple
and prove that it works.
We can worry about load on demand later if we still want it at that point.
--js
next prev parent reply other threads:[~2021-06-10 14:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAN6ztm-J2GoQKkLb=Az0H2Q8UKK4oE3PgXg7g14=T53sQAUyDg@mail.gmail.com>
2021-05-21 19:02 ` Fwd: GSoC Intro - TUI interface for QMP Niteesh G. S.
2021-05-24 13:32 ` Stefan Hajnoczi
2021-05-24 17:34 ` John Snow
2021-06-02 11:08 ` Bruno Piazera Larsen
2021-06-11 14:06 ` Vladimir Sementsov-Ogievskiy via
2021-05-26 15:35 ` Fwd: " Niteesh G. S.
2021-06-01 23:47 ` John Snow
2021-06-08 15:01 ` Markus Armbruster
2021-06-08 15:49 ` John Snow
2021-06-09 11:56 ` Markus Armbruster
2021-06-09 17:06 ` John Snow
2021-06-10 7:19 ` Markus Armbruster
2021-06-09 12:07 ` Daniel P. Berrangé
2021-06-10 14:35 ` John Snow [this message]
2021-06-09 12:03 ` Daniel P. Berrangé
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=bb073532-6d90-4a3d-80a0-93bfad45b10d@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kwolf@redhat.com \
--cc=niteesh.gs@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wainersm@redhat.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 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.