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 76431489AA; Thu, 23 Oct 2025 02:36:57 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5870940151; Thu, 23 Oct 2025 02:36:57 +0200 (CEST) Received: from mail-pg1-f179.google.com (mail-pg1-f179.google.com [209.85.215.179]) by mails.dpdk.org (Postfix) with ESMTP id 31585400D6 for ; Thu, 23 Oct 2025 02:36:55 +0200 (CEST) Received: by mail-pg1-f179.google.com with SMTP id 41be03b00d2f7-b6cf30e5bbcso244759a12.0 for ; Wed, 22 Oct 2025 17:36:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1761179814; x=1761784614; 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=+5O9UiZRLzeXAxOJh7hIReQ+tGS+Xr2TmUVLFC+ABnA=; b=EKFl3DH+ZFD/09FSMp4DmB7TiAf2aZ91JGR4yQiMV64KOzhz5zNJfBVF3+oDj3bVs+ 1wYcdXAHyDayXBPGiyOANmt/TpzYy/VBHp2CVSnjLlHpeoil27+6k346aBLyh+KmatAm pMZ3R1F+GJNv4IvLhLq2gu0NeOYjudeMtm1wY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761179814; x=1761784614; 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=+5O9UiZRLzeXAxOJh7hIReQ+tGS+Xr2TmUVLFC+ABnA=; b=eTWJkabAv17TasrCfuIRMDn+FvCtudy3t5TBDY9rSJqGuqHKvjbk2jf0TYqZYYbEa6 85zub58cvF791qm1GiAWCxThPuZEsCFKESzy+AkuiqF/wbpGNlh/ji+NrP1+4Gegc2D8 VkryXn29PjVLq3I/9FsxaoS69jhGV1uV1So+A0/x+mQ0jSbyQlZ6oxfFxD7FSryZLFdA YGmG2yVBfhHXkvaT60+pt1TG8RhVepbYwCnfivO5OxSY6Ple4BaqFQqg1m+QK5dpnZmf s0BkvMJ9o2Ga3T7DdF5tGbY+9Duiu5i6mY7uXirg60vczsYB9YBwTZ7gW7tpGlkV6v0y oOTA== X-Forwarded-Encrypted: i=1; AJvYcCU8adWX02DHmZlmGyIsosPvWsURBtcTFH398/9tYndxkm1sJAG3snU9po670X7KxEhieg==@dpdk.org X-Gm-Message-State: AOJu0Yx29R3JE/qcbT2uLVC6YB28MzdOIA3tNNc81Fv0Wl/d5xkDj9ws lYGSwuU5pJdlyvQ2XqHVTzsbB1gyE+TFBs74I2z+2dM1432uCtqIFiTw34hB9ld6BqdAAV98zwv MVf4ReyYt5tfz1ybOCk+rkdlJ1sCmZQl47LgTHd3pDg== X-Gm-Gg: ASbGncvf32e3pZSpcpOxdtmMz/R2gmiKqkbANjdpSk/xTh6+FZxcS3qThO1Qy/FXLPs STaYAQSlM5UsqtYTCeMC3NWDYTWc313ctHSYoqwoOgV7UNnN53osGOm71rV/W6eRh+c3UpNapay aIAfOQVyFSg3WA4ePOv1O56UmDS3aiMGCl4TRhkNWu/RKkITZMyVTxD3gaQkrnHIZYhpx/R+niv Afmd3UKRZSYpx9DaViS8J0tL3TmGBrjRsEWD9nRVnkZVEyQtGjeuJfvB63pkStrsUqGgy7Q0NI4 XBwx2+P5RZ6RxYIipQ== X-Google-Smtp-Source: AGHT+IHyck3QTpPFNzzHwU0CEFGqUhnboeGU3TyiJsb0VnMURqD8yjJmXmJYTcHFVRUfyGqfU9n6FAOH7AOyRynm9us= X-Received: by 2002:a17:903:1ae4:b0:265:e815:fcdf with SMTP id d9443c01a7336-2935e0b4f3amr40208875ad.17.1761179814077; Wed, 22 Oct 2025 17:36:54 -0700 (PDT) MIME-Version: 1.0 References: <6873353.2l3rmUXbR5@thomas> In-Reply-To: From: Patrick Robb Date: Wed, 22 Oct 2025 20:36:01 -0400 X-Gm-Features: AS18NWAaNbTIvxHsXDcX5WSaHH4U8Sa3PxFolKFZHq8QTzDK6aE-1uFkyrBsg-w Message-ID: Subject: Re: BNXT patches To: Ajit Khaparde Cc: Thomas Monjalon , ci@dpdk.org, Ali Alnubani Content-Type: multipart/alternative; boundary="00000000000034367f0641c8a1d8" 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 --00000000000034367f0641c8a1d8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable There are multiple next-net-brcm branches at https://git.dpdk.org/next/dpdk-next-net-brcm/. I have chosen the for-next-net branch. Let me know if I should adjust. So, you can go to https://lab.dpdk.org/results/dashboard/periodic_testing/ and select the "showing branch" dropdown on the right and select "next-net-brcm-for-next-net" I kicked off a run from that branch so it should populate a new set of results within a couple hours. Then like I said a new run of that branch will kick off every 48 hours. Good luck! On Wed, Oct 22, 2025 at 8:09=E2=80=AFPM Ajit Khaparde wrote: > On Wed, Oct 22, 2025 at 4:52=E2=80=AFPM Patrick Robb = wrote: > > > > That solution also makes sense. > Agree. Thanks Thomas. > > > > > 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. > > Yes, Patrick, this should work. > > > > > 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 an= y > 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 o= n > the > >> > 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 > companies. > >> > > >> > 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" > idea > >> > 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 > >> > >> > >> > >> > --00000000000034367f0641c8a1d8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
There are multiple next-net-brcm branches at=C2=A0https://git.dpdk.org/nex= t/dpdk-next-net-brcm/. I have chosen the for-next-net branch. Let me kn= ow if I should adjust.

So, you can go to=C2=A0https://lab.dpdk= .org/results/dashboard/periodic_testing/ and select the "showing b= ranch" dropdown on the right and select "next-net-brcm-for-next-n= et"

I kicked off a run from that branch so it= should populate a new set of results within a couple hours. Then like I sa= id a new run of that branch will kick off every 48 hours.=C2=A0
<= br>
Good luck!

On Wed, Oct 22, 2025 at= 8:09=E2=80=AFPM Ajit Khaparde <ajit.khaparde@broadcom.com> wrote:
On Wed, Oct 22, 2025 at 4:52=E2=80=AFPM Pa= trick Robb <probb= @iol.unh.edu> wrote:
>
> That solution also makes sense.
Agree. Thanks Thomas.

>
> For the per-branch periodic testing page that Thomas is mentioning (he= re: https://lab.dpdk.org/results/dashboard/p= eriodic_testing/) we are publishing regular test reports on next-net, b= ut 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 f= irst periodic testrun for next-net-brcm. Otherwise, it should run once ever= y other day at midnight US eastern time.
>
> Let us know if this solution works for you Ajit. Thanks.

Yes, Patrick, this should work.

>
> On Wed, Oct 22, 2025 at 7:36=E2=80=AFPM Thomas Monjalon <thomas@monjalon.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 t= here any sense
>> > in resubmitting the series and just intentionally delaying se= nding 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 sol= ution on the
>> > 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 r= estriction for
>> > emails coming from email addresses associated with DPDK membe= r companies.
>> >
>> > 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 &= quot;bundle" idea
>> > 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 you= r series) and
>> > allowing the CI system automation to intake the patchseries f= rom 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 restric= tion,
>> > > only 31 of 57 patches went through in the first attempt<= br> >> > >
>> > > He submitted the remaining patches 32 to 57 in second at= tempt.
>> > >
>> > > 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://m= ails.dpdk.org/archives/test-report/2025-October/921500.html
>> > >
>> > > Thanks
>> > > Ajit
>>
>>
>>
>>
--00000000000034367f0641c8a1d8--