From: Tom Rini <trini@konsulko.com>
To: seanedmond@linux.microsoft.com
Cc: u-boot@lists.denx.de, xypron.glpk@gmx.de, pbrobinson@gmail.com
Subject: Re: [PATCH v4 0/3] [PATCH v4 0/3] [PATCH v3 0/3] BOOTP/DHCPv4 enhancements
Date: Fri, 17 Nov 2023 17:10:02 -0500 [thread overview]
Message-ID: <20231117221002.GC170968@bill-the-cat> (raw)
In-Reply-To: <20231117214925.138486-1-seanedmond@linux.microsoft.com>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
On Fri, Nov 17, 2023 at 01:49:22PM -0800, seanedmond@linux.microsoft.com wrote:
> 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.
The changes from revision to revision should be below the "---" in a
commit and not the commit message itself. Please reword things for v5.
Thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-11-17 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 21:49 [PATCH v4 0/3] [PATCH v4 0/3] [PATCH v3 0/3] BOOTP/DHCPv4 enhancements seanedmond
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 ` Tom Rini [this message]
2023-11-18 17:10 ` [PATCH v4 0/3] [PATCH v4 0/3] [PATCH v3 0/3] BOOTP/DHCPv4 enhancements 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=20231117221002.GC170968@bill-the-cat \
--to=trini@konsulko.com \
--cc=pbrobinson@gmail.com \
--cc=seanedmond@linux.microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.