On 1/29/26 11:51 PM, Mehrdad Moradi via dev wrote: > Subject: [PATCH v3] pinctrl: Randomize DNS response IP order for load > balancing. > > When ovn-controller returns DNS responses with multiple IP addresses, > clients typically use the first IP in the list. Without randomization, > all clients direct traffic to the same backend, leading to uneven load > distribution. > > This patch implements Fisher-Yates shuffle on IPv4 and IPv6 address > arrays before building DNS answers, ensuring each query returns IPs > in a randomized order for better traffic distribution across backends. > > Signed-off-by: Mehrdad Moradi <[email protected]> > --- > v3: Fixed test script - removed 'local' keywords outside of functions > v2: Updated tests to handle randomized IP ordering in DNS responses > --- > controller/pinctrl.c | 40 +++++++++++++++++++++++++++++++ > tests/ovn.at | 56 +++++++++++++++++++++++++++++++++++++++----- > 2 files changed, 90 insertions(+), 6 deletions(-)
Hi, Mehrdad. Thanks for the patch! This patch is for OVN, so it should have [PATCH ovn v3] subject prefix instead of simple [PATCH v3]. The "ovn" part signals to which patchwork instance this patch should go and where to apply it for CI. As you may have noticed, your change went into OVS patchwork and the 0-day robot attempted to apply it to OVS tree for testing and failed. Also, each version supposed to be a separate email, i.e. not a reply to a previous version and no quoting the previous emails. And the subject line should be the actual subject line, not a one embedded into the body of the email. Otherwise patchwork doesn't recognize them as separate patches. In general, I'd suggest to use 'git send-email' for sending patches, as it will take care of most of the aspects of patch submission for you. Also, try to not send more than one version per day to give reviewers some time to look at your patch and avoid clogging CI pipelines. Note that it normally takes quite a bit longer than one day to get some feedback. You can test your changes locally before submitting the patch, or you can use your own GitHub account to run most of the CI with GitHub Actions. Best regards, Ilya Maximets. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
