From: seanedmond@linux.microsoft.com
To: u-boot@lists.denx.de
Cc: joe.hershberger@ni.com, rfried.dev@gmail.com, sjg@chromium.org,
xypron.glpk@gmx.de, ilias.apalodimas@linaro.org
Subject: [PATCH v2 0/3] BOOTP/DHCPv4 enhancements
Date: Mon, 23 Oct 2023 17:21:56 -0700 [thread overview]
Message-ID: <20231024002159.74477-1-seanedmond@linux.microsoft.com> (raw)
From: Sean Edmond <seanedmond@microsoft.com>
In our datacenter application, a single DHCP server is servicing 36000+ clients.
Improvements are required to the DHCPv4 retransmission behavior to align with
RFC and ensure less pressure is exerted on the server:
- retransmission backoff interval maximum is configurable
(environment variable bootpretransmitperiodmax)
- initial retransmission backoff interval is configurable
(environment variable bootpretransmitperiodinit)
- transaction ID is kept the same for each BOOTP/DHCPv4 request
(not recreated on each retry)
For our application we'll use:
- bootpretransmitperiodmax=16000
- bootpretransmitperiodinit=2000
A new configuration BOOTP_RANDOM_XID has been added to enable a randomized
BOOTP/DHCPv4 transaction ID.
Add functionality for DHCPv4 sending/parsing option 209 (PXE config file).
Enabled with Kconfig BOOTP_PXE_DHCP_OPTION. Note, this patch was
submitted previously but this latest version has been enhanced to
avoid a possible double free().
changes in v2:
- use env_get_ulong() to get environment variables
Sean Edmond (3):
net: Get pxe config file from dhcp option 209
net: bootp: BOOTP/DHCPv4 retransmission improvements
net: bootp: add config option BOOTP_RANDOM_XID
cmd/Kconfig | 11 ++++++++
cmd/pxe.c | 10 +++++++
net/bootp.c | 78 ++++++++++++++++++++++++++++++++++++++++++-----------
3 files changed, 84 insertions(+), 15 deletions(-)
--
2.40.0
next reply other threads:[~2023-10-24 0:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 0:21 seanedmond [this message]
2023-10-24 0:21 ` [PATCH v2 1/3] net: Get pxe config file from dhcp option 209 seanedmond
2023-10-24 5:54 ` Heinrich Schuchardt
2023-10-24 13:52 ` Peter Robinson
2023-11-04 1:03 ` Sean Edmond
2023-11-04 7:53 ` Heinrich Schuchardt
2023-11-07 23:50 ` Sean Edmond
2023-11-08 0:23 ` Tom Rini
2023-11-08 12:24 ` Peter Robinson
2023-11-09 21:04 ` Tom Rini
2023-11-09 21:35 ` Heinrich Schuchardt
2023-11-09 21:40 ` Tom Rini
2023-10-24 0:21 ` [PATCH v2 2/3] net: bootp: BOOTP/DHCPv4 retransmission improvements seanedmond
2023-10-24 6:06 ` Heinrich Schuchardt
2023-10-24 16:42 ` Sean Edmond
2023-11-04 1:04 ` Sean Edmond
2023-11-04 7:48 ` Heinrich Schuchardt
2023-10-24 0:21 ` [PATCH v2 3/3] net: bootp: add config option BOOTP_RANDOM_XID seanedmond
2023-10-24 6:19 ` Heinrich Schuchardt
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=20231024002159.74477-1-seanedmond@linux.microsoft.com \
--to=seanedmond@linux.microsoft.com \
--cc=ilias.apalodimas@linaro.org \
--cc=joe.hershberger@ni.com \
--cc=rfried.dev@gmail.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--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