From: seanedmond@linux.microsoft.com
To: u-boot@lists.denx.de
Cc: xypron.glpk@gmx.de, pbrobinson@gmail.com, trini@konsulko.com
Subject: [PATCH v4 0/3] [PATCH v4 0/3] [PATCH v3 0/3] BOOTP/DHCPv4 enhancements
Date: Fri, 17 Nov 2023 13:49:22 -0800 [thread overview]
Message-ID: <20231117214925.138486-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.
Enhance DHCPv4 sending/parsing option 209 (PXE config file). A previous
patch was accepted. A new patch fixes a possible double free() and
addresses latest review comments.
changes in v4:
- rebase master and resolve conflicts
- change commit description for DHCP option 209 patch (this is now
an enhancement patch)
- default y for BOOTP_PXE_DHCP_OPTION (feedback from review)
- Add "select LIB_RAND" for "config CMD_BOOTP" (retransmission
improvements require rand())
changes in v3:
- add define for option 209 and rfc5071 reference
- Set RETRANSMIT_PERIOD_MAX_MS=60000
- Add randomization factor to retransmission timeout
- Add depends for BOOTP_RANDOM_XID
changes in v2:
- use env_get_ulong() to get environment variables
Sean Edmond (3):
net: Additional fixes for dhcp option 209
net: bootp: BOOTP/DHCPv4 retransmission improvements
net: bootp: add config option BOOTP_RANDOM_XID
cmd/Kconfig | 10 ++++++-
cmd/pxe.c | 2 ++
net/bootp.c | 76 +++++++++++++++++++++++++++++++++++++++++------------
net/bootp.h | 2 ++
4 files changed, 72 insertions(+), 18 deletions(-)
--
2.42.0
next reply other threads:[~2023-11-17 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 21:49 seanedmond [this message]
2023-11-17 21:49 ` [PATCH v4 1/3] net: Additional fixes for dhcp option 209 seanedmond
2023-11-17 21:49 ` [PATCH v4 2/3] net: bootp: BOOTP/DHCPv4 retransmission improvements seanedmond
2023-11-17 21:49 ` [PATCH v4 3/3] net: bootp: add config option BOOTP_RANDOM_XID seanedmond
2023-11-17 22:08 ` Tom Rini
2023-11-17 22:10 ` [PATCH v4 0/3] [PATCH v4 0/3] [PATCH v3 0/3] BOOTP/DHCPv4 enhancements Tom Rini
2023-11-18 17:10 ` Simon Glass
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=20231117214925.138486-1-seanedmond@linux.microsoft.com \
--to=seanedmond@linux.microsoft.com \
--cc=pbrobinson@gmail.com \
--cc=trini@konsulko.com \
--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