diff options
| author | Tom Rini <trini@konsulko.com> | 2025-05-23 11:29:55 -0600 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2025-05-23 11:31:03 -0600 |
| commit | da24eb55327978410f5559f44ce1434ae8d8932d (patch) | |
| tree | 441736e6e7c79637a61b8f0dab9cac2260e1e4be /lib/efi_loader/efi_bootmgr.c | |
| parent | ef305ceff9c875a7c16fdffc5e120d8ddf6243b7 (diff) | |
| parent | 2111bd7e93a3044f0590c942a41f2667d15d923d (diff) | |
Merge patch series "BOOTP/DHCPv4 enhancements"
Sean Edmond <seanedmond@microsoft.com> says:
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.
Link: https://lore.kernel.org/r/20240509023918.2504185-1-seanedmond@microsoft.com
Diffstat (limited to 'lib/efi_loader/efi_bootmgr.c')
0 files changed, 0 insertions, 0 deletions