From: Tom Rini <trini@konsulko.com>
To: Ilias Apalodimas <ilias.apalodimas@linaro.org>
Cc: Maxim Uvarov <maxim.uvarov@linaro.org>,
u-boot@lists.denx.de, pbrobinson@redhat.com,
joe.hershberger@ni.com, rfried.dev@gmail.com
Subject: Re: [RFC PATCH 0/5] LWIP stack integration
Date: Mon, 22 May 2023 10:20:48 -0400 [thread overview]
Message-ID: <20230522142048.GA8649@bill-the-cat> (raw)
In-Reply-To: <CAC_iWjK6z89XLfCpkeM2qgHpOaeMV7SefdCCp_5k1ELvy87_=Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
On Mon, May 22, 2023 at 04:33:57PM +0300, Ilias Apalodimas wrote:
> Hi Maxim
>
> On Mon, 22 May 2023 at 12:01, Maxim Uvarov <maxim.uvarov@linaro.org> wrote:
> >
> > My measurements for binary after LTO looks like:
> >
> > U-boot WGET | LWIP WGET + ping | LWIP WGET| diff bytes| diff %
> > 870728 | 915000 | 912560 | 41832 | 4.8
>
>
> I think you'll need to analyze that a bit more. First of all I don't
> think the '+ping' tab is useful. What is is trying to achieve?
> - How was LWIP compiled?
> - Was ipv6 supported?
> - Can we strip it down even further?
>
> In general please give as much information as you can with what we
> gain in functionality from LWIP with those extra bytes of code.
And please make sure to disable the previous support, my guess fro that
much growth is that you didn't.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-05-22 14:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 10:25 [RFC PATCH 0/5] LWIP stack integration Maxim Uvarov
2023-05-05 10:25 ` [RFC PATCH 1/5] add lwip-external submodule Maxim Uvarov
2023-05-08 14:43 ` Simon Glass
2023-05-10 7:40 ` Ilias Apalodimas
2023-05-10 14:46 ` Peter Robinson
2023-05-11 13:51 ` Tom Rini
2023-05-11 13:51 ` Tom Rini
2023-05-05 10:25 ` [RFC PATCH 2/5] lib/lwip: compile-in core files Maxim Uvarov
2023-05-05 10:25 ` [RFC PATCH 3/5] add doc/README.lwip Maxim Uvarov
2023-05-11 13:51 ` Tom Rini
2023-05-05 10:25 ` [RFC PATCH 4/5] add doc/README.lwip.size Maxim Uvarov
2023-05-11 13:51 ` Tom Rini
2023-05-05 10:25 ` [RFC PATCH 5/5] lwip: implement wget command from http_client.c example Maxim Uvarov
2023-05-05 10:27 ` [RFC PATCH 0/5] LWIP stack integration Ilias Apalodimas
2023-05-08 21:23 ` Simon Glass
2023-05-11 13:28 ` Maxim Uvarov
2023-05-11 13:52 ` Tom Rini
2023-05-15 15:25 ` Maxim Uvarov
2023-05-15 15:39 ` Tom Rini
2023-05-19 13:17 ` Ilias Apalodimas
2023-05-19 13:52 ` Tom Rini
2023-05-22 9:01 ` Maxim Uvarov
2023-05-22 13:33 ` Ilias Apalodimas
2023-05-22 14:20 ` Tom Rini [this message]
2023-05-22 16:40 ` Maxim Uvarov
2023-05-22 21:23 ` Tom Rini
2023-05-24 14:05 ` Maxim Uvarov
2023-05-24 20:18 ` [lwip-devel] " Simon Goldschmidt
2023-06-06 14:33 ` Maxim Uvarov
2023-06-07 9:46 ` Ilias Apalodimas
2023-06-07 12:01 ` Maxim Uvarov
2023-06-11 8:24 ` Simon Glass
2023-06-11 18:34 ` Tom Rini
2023-06-07 20:07 ` Tom Rini
2023-06-08 10:14 ` Maxim Uvarov
2023-06-08 17:52 ` Ilias Apalodimas
2023-06-09 7:37 ` Peter Robinson
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=20230522142048.GA8649@bill-the-cat \
--to=trini@konsulko.com \
--cc=ilias.apalodimas@linaro.org \
--cc=joe.hershberger@ni.com \
--cc=maxim.uvarov@linaro.org \
--cc=pbrobinson@redhat.com \
--cc=rfried.dev@gmail.com \
--cc=u-boot@lists.denx.de \
/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