From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7F9E9489A9; Thu, 23 Oct 2025 01:52:59 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5A6A740262; Thu, 23 Oct 2025 01:52:59 +0200 (CEST) Received: from mail-pj1-f54.google.com (mail-pj1-f54.google.com [209.85.216.54]) by mails.dpdk.org (Postfix) with ESMTP id 11EF14025E for ; Thu, 23 Oct 2025 01:52:58 +0200 (CEST) Received: by mail-pj1-f54.google.com with SMTP id 98e67ed59e1d1-33bcf228ee4so204502a91.1 for ; Wed, 22 Oct 2025 16:52:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1761177177; x=1761781977; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=+3Hqma+tnSdSk0y/wadYueaJ0pjhQii69WVg9fs+9bE=; b=GQfHQeDuZ+ChZMhRSOh4rBqfQ3z2PXeghSpXaX1rwyVRoP9AW7gV6IJEN8IOJqFMGu WzAK3j/yzO4wXaRYZ/FvvhKdgCCS/bCGveQguCCzHeWUGjFxXA3lVsVR5g2wVAoVWgY5 +j9ckLMgRxip1iU+zx1opML+D/iKY40gg/7T8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761177177; x=1761781977; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+3Hqma+tnSdSk0y/wadYueaJ0pjhQii69WVg9fs+9bE=; b=pXoyfxOEMTY23nQkRmd7ZTD7hVELyPcBi9jcyX0EA5y09trqA5o0suPUjvjzlUeWKp Kt30BOBOGRN3FHezUOM57RiWPd/zRtdhDAtOqQCyyuAzRANN7kh7zyCbhNc0aiKyY5ZC A7P8q+qO2kGvw1rT478nUSovzORpyOkT081/SgsEYBLfvOFCMvzQJhgFxW34oYSGK9le hQ/huiT9Afd8DNVWuc30466YGPK0zZWielA8x9NYejqAKyyBUx2juO1AuzabQAq0LXkt cBKA+U/UM1VHFca7T0ozDhyBA8FugU/MDNkx0tRTd7G/sSxER1bczyjO5ads9KW7k6zx FJ5A== X-Forwarded-Encrypted: i=1; AJvYcCVfeRzfA7BuApAScJSeWr+oNR74eeqNwDzLCa27zu+O2sW6EF0IeVoxv8Jl27yXmFre1Q==@dpdk.org X-Gm-Message-State: AOJu0YwksDM4dT852s73aBWYLsQjGFLwxqaGaG+VAtaOaVYucruQqFUB ZNw0kSuABN5SYx9aOMWTnDKSwDPmQjAiV5et5MlmfN/Dk0Sbrp5UxckPCH6IpNhzGeDs7qhFN+B 5jhMSySFOpR+QpclJeABNM8PEzk0t2ljhLPFGiUQjMA== X-Gm-Gg: ASbGncs/5vxu696CfOjFCJGzx5doLlF613C/+aEwWo2fD07cNDFCgbXO5jQ7LzfqAzU 2/M6byjQdFJr+EVbX29qt7uCNTNupYFAtNYTDKSO4L81RkL7BXz7Gd4Ku6wqY4/KKXk4arqop+Y LMCUVL2cmKdKO7vnG2FA6WNuOzj9HsJk9+LmR5KN7yAWqVyvRnFXEhDKy9fjwnoa3nfSmSHEoF5 SCM74Z0oYkSZH1xJ9yqjlwxu7qAsXQ8rQHgLM6OJFEQ2LwLq+YV13+4NjwXSpPHpp7aLM55dEdH n7UlHNxRgNOO8E2Haw== X-Google-Smtp-Source: AGHT+IHvaoEZWg6UFWbvKeLhn1seWxjkaD5kyCPFWcwLgD/Ck2l/dGSSvCk/d44Eb9a6pyE+JPWo9dAN3MMH/bH4WdM= X-Received: by 2002:a17:902:f548:b0:25f:fe5f:c927 with SMTP id d9443c01a7336-290ca1214e1mr321687285ad.31.1761177176878; Wed, 22 Oct 2025 16:52:56 -0700 (PDT) MIME-Version: 1.0 References: <6873353.2l3rmUXbR5@thomas> In-Reply-To: <6873353.2l3rmUXbR5@thomas> From: Patrick Robb Date: Wed, 22 Oct 2025 19:52:05 -0400 X-Gm-Features: AS18NWBr_-VrXVvcfb9eEl9APfs98GfadewQxY_BirrxX9l3cao0DfG0477zOrs Message-ID: Subject: Re: BNXT patches To: Thomas Monjalon Cc: Ajit Khaparde , ci@dpdk.org, Ali Alnubani Content-Type: multipart/alternative; boundary="00000000000003be210641c804af" X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org --00000000000003be210641c804af Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable That solution also makes sense. For the per-branch periodic testing page that Thomas is mentioning (here: https://lab.dpdk.org/results/dashboard/periodic_testing/) we are publishing regular test reports on next-net, but not next-net-brcm. But, it makes sense for us to start periodic runs on next-net-brcm, so I will add this now. It should only take a few minutes to add to our CI system. Then I will do a manual trigger which will add the first periodic testrun for next-net-brcm. Otherwise, it should run once every other day at midnight US eastern time. Let us know if this solution works for you Ajit. Thanks. On Wed, Oct 22, 2025 at 7:36=E2=80=AFPM Thomas Monjalon wrote: > Hello, > > Not related to CI, but the best would be to not wait a year > for updating the driver in one series. > > As you maintain a repository branch, > you can merge the patches and wait for UNH CI running on it. > Also the GitHub robot can run if you push in a GitHub repo. > > > 23/10/2025 01:05, Patrick Robb: > > Hi Ajit, > > > > That sounds annoying. A sanity check question to start - is there any > sense > > in resubmitting the series and just intentionally delaying sending the > 2nd > > half of the commits? I.e. > > > > 1. git send-email /my-patches-dir/* > > 2. Send the first 30 > > 3. At prompt for 31st patch, pause. > > 4. wait 10 minutes. > > 5. Return to terminal, send patches 31 through 57. > > > > Or, if this is not possible, I think there should be some solution on t= he > > patchwork mail server policy side. I think Ali Alnubani from NVIDIA > manages > > it and he is usually pretty responsive with such modification requests. > We > > could ask about solutions like: > > > > 1. Add a complete exception to the mail server message rate restriction > for > > emails coming from email addresses associated with DPDK member companie= s. > > > > or > > > > 2. Simply make the message rate restrictions more permissive than they > are > > currently (i.e. allow 100 emails, not 30). > > > > If the ideas above will not work, I will have to assess the "bundle" id= ea > > tomorrow when I have time available than I do right now. Most likely it= 's > > technically possible to facilitate but I do feel like simply resolving > the > > original issue (the mail server is not letting you submit your series) > and > > allowing the CI system automation to intake the patchseries from > patchwork > > in the normal way is the ideal approach. > > > > On Wed, Oct 22, 2025 at 5:39=E2=80=AFPM Ajit Khaparde < > ajit.khaparde@broadcom.com> > > wrote: > > > > > Hi Patrick, > > > When Manish was submitting his patchset, > > > Looks like because of a mail server message rate restriction, > > > only 31 of 57 patches went through in the first attempt > > > > > > He submitted the remaining patches 32 to 57 in second attempt. > > > > > > I created a bundle for the series now. [1] > > > > > > Also a couple of patches were stuck at the gate. > > > So a proper build has not happened on the patchset yet. [2] > > > Do we have a way to trigger a build on the bundle? > > > > > > Please advise. > > > > > > [1] https://patchwork.dpdk.org/bundle/ajitkhaparde/BNXT%2025.11/ > > > [2] > https://mails.dpdk.org/archives/test-report/2025-October/921500.html > > > > > > Thanks > > > Ajit > > > > > --00000000000003be210641c804af Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
That solution also makes sense.

For the= per-branch periodic testing page that Thomas is mentioning (here:=C2=A0https://l= ab.dpdk.org/results/dashboard/periodic_testing/) we are publishing regu= lar test reports on next-net, but not next-net-brcm. But, it makes sense fo= r us to start periodic runs on next-net-brcm, so I will add this now. It sh= ould only take a few minutes to add to our CI system. Then I will do a manu= al trigger which will add the first periodic testrun for next-net-brcm. Oth= erwise, it should run once every other day at midnight US eastern time.

Let us know if this solution works for you Ajit. Than= ks.=C2=A0

<= div dir=3D"ltr" class=3D"gmail_attr">On Wed, Oct 22, 2025 at 7:36=E2=80=AFP= M Thomas Monjalon <thomas@monjalo= n.net> wrote:
Hello,

Not related to CI, but the best would be to not wait a year
for updating the driver in one series.

As you maintain a repository branch,
you can merge the patches and wait for UNH CI running on it.
Also the GitHub robot can run if you push in a GitHub repo.


23/10/2025 01:05, Patrick Robb:
> Hi Ajit,
>
> That sounds annoying. A sanity check question to start - is there any = sense
> in resubmitting the series and just intentionally delaying sending the= 2nd
> half of the commits? I.e.
>
> 1. git send-email /my-patches-dir/*
> 2. Send the first 30
> 3. At prompt for 31st patch, pause.
> 4. wait 10 minutes.
> 5. Return to terminal, send patches 31 through 57.
>
> Or, if this is not possible, I think there should be some solution on = the
> patchwork mail server policy side. I think Ali Alnubani from NVIDIA ma= nages
> it and he is usually pretty responsive with such modification requests= . We
> could ask about solutions like:
>
> 1. Add a complete exception to the mail server message rate restrictio= n for
> emails coming from email addresses associated with DPDK member compani= es.
>
> or
>
> 2. Simply make the message rate restrictions more permissive than they= are
> currently (i.e. allow 100 emails, not 30).
>
> If the ideas above will not work, I will have to assess the "bund= le" idea
> tomorrow when I have time available than I do right now. Most likely i= t's
> technically possible to facilitate but I do feel like simply resolving= the
> original issue (the mail server is not letting you submit your series)= and
> allowing the CI system automation to intake the patchseries from patch= work
> in the normal way is the ideal approach.
>
> On Wed, Oct 22, 2025 at 5:39=E2=80=AFPM Ajit Khaparde <ajit.khaparde@broadcom.= com>
> wrote:
>
> > Hi Patrick,
> > When Manish was submitting his patchset,
> > Looks like because of a mail server message rate restriction,
> > only 31 of 57 patches went through in the first attempt
> >
> > He submitted the remaining patches 32 to 57 in second attempt. > >
> > I created a bundle for the series now. [1]
> >
> > Also a couple of patches were stuck at the gate.
> > So a proper build has not happened on the patchset yet. [2]
> > Do we have a way to trigger a build on the bundle?
> >
> > Please advise.
> >
> > [1] https://patchwork.dpdk.org= /bundle/ajitkhaparde/BNXT%2025.11/
> > [2] https://mails.dpdk= .org/archives/test-report/2025-October/921500.html
> >
> > Thanks
> > Ajit




--00000000000003be210641c804af--