public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Sean Edmond <seanedmond@microsoft.com>
Cc: u-boot@lists.denx.de,
	"AKASHI Takahiro" <takahiro.akashi@linaro.org>,
	"Bin Meng" <bmeng.cn@gmail.com>,
	"Charles Hardin" <ckhardin@gmail.com>,
	"Heinrich Schuchardt" <xypron.glpk@gmx.de>,
	"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
	"Joe Hershberger" <joe.hershberger@ni.com>,
	"Michal Simek" <michal.simek@amd.com>,
	"Oleksandr Suvorov" <oleksandr.suvorov@foundries.io>,
	"Ramon Fried" <rfried.dev@gmail.com>,
	"Sean Anderson" <sean.anderson@seco.com>,
	"Simon Glass" <sjg@chromium.org>,
	"Vincent Stehlé" <vincent.stehle@arm.com>
Subject: Re: [PATCH v6 2/3] net: bootp: BOOTP/DHCPv4 retransmission improvements
Date: Wed, 8 May 2024 09:32:47 -0600	[thread overview]
Message-ID: <20240508153247.GA3129288@bill-the-cat> (raw)
In-Reply-To: <20240429183449.2284935-3-seanedmond@microsoft.com>

[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]

On Mon, Apr 29, 2024 at 11:33:57AM -0700, Sean Edmond wrote:

> This patch introduces 3 improvements to align with RFC 951:
> - retransmission backoff interval maximum is configurable
> - initial retranmission backoff interval is configurable
> - transaction ID is kept the same for each BOOTP/DHCPv4 request
> 
> In applications where thousands of nodes are serviced by a single DHCP
> server, maximizing the retransmission backoff interval at 2 seconds (the
> current u-boot default) exerts high pressure on the DHCP server and
> network layer.
> 
> RFC 951 “7.2. Client Retransmission Strategy” states that the
> retransmission backoff interval should be limited to 60 seconds.  This
> patch allows the interval to be configurable using the environment
> variable "bootpretransmitperiodmax"
> 
> The initial retranmission backoff period defaults to 250ms, which is
> also too small for these scenarios with many clients.  This patch makes
> the initial retransmission interval to be configurable using the
> environment variable "bootpretransmitperiodinit".
> 
> Also, on a retransmission it is not expected for the transaction ID to
> change (only the 'secs' field should be updated). Let's save the
> transaction ID and use the same transaction ID for each BOOTP/DHCPv4
> exchange.
> 
> Signed-off-by: Sean Edmond <seanedmond@microsoft.com>

On numerous platforms we now get:
+(imx8qm_dmsse20a1) WARNING 'mx8qm-ahab-container.img' not found, resulting binary is not-functional
+(imx8qm_dmsse20a1) net/bootp.c: In function 'bootp_reset':
+(imx8qm_dmsse20a1) net/bootp.c:741:15: error: unused variable 'ep' [-Werror=unused-variable]
+(imx8qm_dmsse20a1)   741 |         char *ep;  /* Environment pointer */
+(imx8qm_dmsse20a1)       |               ^~
+(imx8qm_dmsse20a1) cc1: all warnings being treated as errors
+(imx8qm_dmsse20a1) make[2]: *** [scripts/Makefile.build:257: net/bootp.o] Error 1
+(imx8qm_dmsse20a1) make[1]: *** [Makefile:1892: net] Error 2
+(imx8qm_dmsse20a1) make: *** [Makefile:177: sub-make] Error 2

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2024-05-08 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 18:33 [PATCH v6 0/3] BOOTP/DHCPv4 enhancements Sean Edmond
2024-04-29 18:33 ` [PATCH v6 1/3] net: Enhancements for dhcp option 209 Sean Edmond
2024-04-29 18:33 ` [PATCH v6 2/3] net: bootp: BOOTP/DHCPv4 retransmission improvements Sean Edmond
2024-05-08 15:32   ` Tom Rini [this message]
2024-04-29 18:33 ` [PATCH v6 3/3] net: bootp: add config option BOOTP_RANDOM_XID Sean Edmond
  -- strict thread matches above, loose matches on Subject: below --
2023-11-22 23:27 [PATCH v6 0/3] BOOTP/DHCPv4 enhancements Sean Edmond
2023-11-22 23:27 ` [PATCH v6 2/3] net: bootp: BOOTP/DHCPv4 retransmission improvements Sean Edmond
2024-03-26 23:58   ` Tom Rini

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=20240508153247.GA3129288@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=bmeng.cn@gmail.com \
    --cc=ckhardin@gmail.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=joe.hershberger@ni.com \
    --cc=michal.simek@amd.com \
    --cc=oleksandr.suvorov@foundries.io \
    --cc=rfried.dev@gmail.com \
    --cc=sean.anderson@seco.com \
    --cc=seanedmond@microsoft.com \
    --cc=sjg@chromium.org \
    --cc=takahiro.akashi@linaro.org \
    --cc=u-boot@lists.denx.de \
    --cc=vincent.stehle@arm.com \
    --cc=xypron.glpk@gmx.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