Thanks, this should help greatly going forward in the community lab.
As it relates to our arm64 unit testing, I will give it a few days (or
longer if needed) for next branches to rebase off of main and then
re-enable arm64 unit testing with the eal_flags_file_prefix_autotest added
to the skipped l
Recheck-request: iol-unit-amd64-testing
Failed for service_autotest on windows. I'm doing a retest to see if it's
reproducible.
On Wed, Oct 4, 2023 at 11:13 AM Aaron Conole wrote:
> Patrick Robb writes:
>
> > Thanks, this should help greatly going forward in the community lab.
> >
> > As it relates to our arm64 unit testing, I will give it a few days (or
> longer if needed) for next branche
Recheck-request: iol-broadcom-Functional
Sorry, this series was affected by an infra failure today.
On Mon, Oct 9, 2023 at 4:03 PM Patrick Robb wrote:
>
>> Hello,
>
> Yes, backporting would be ideal from a CI perspective because without it
> we can't run arm64 testing on LTS tests. But I know there are other
> considerations which also have to be weighed.
>
>
ARM Ampere server test fails on this patch are lab infra-failures (I did
some updates on the server yesterday) and they can be ignored.
ARM Ampere server test fails on this patch are lab infra-failures (I did
some updates on the server yesterday) and they can be ignored.
Recheck-request: iol-unit-amd64-testing
A maintainers file change should not cause eal_flags_misc_autotest to fail,
so I'm queuing a retest for this series.
#
July 11, 2024
Attendees
1. Patrick Robb
2. Juraj Linkeš
3. Alex Chapman
4. Tomas Durovec
5. Jeremy Spewock
6. Adam Hassick
7. Manit Mahajan
8. Dean Marx
Hello Zhoumin,
It looks like Loongarch CI failed to apply this patch, but it worked
at the other labs and locally for Serhii when they were checked out to
next-net.
Maybe your CI did not choose next-net, the right branch? I remember
you saying your CI is based on a fork of the dpdk-ci repo. Perha
Hi Min Zhou,
I am seeing that commit for next-net:
https://git.dpdk.org/next/dpdk-next-net/commit/?id=a6c3ec342ee105e322ffdb21e810cdfd38455c62
If you try to manually apply it on next-net, does it work?
Pasting the logs from our apply process below for context:
```
Trying to checkout branch: o
On Wed, Feb 14, 2024 at 3:17 PM Patrick Robb wrote:
>
>
>
> On Wed, Feb 14, 2024 at 3:00 PM Dumitrescu, Cristian
> wrote:
>>
>>
>>
>> [Cristian]
>> Yes, you are right, we do have a DTS test suite for the pipeline library.
>>
>> It would b
On Mon, Jul 15, 2024 at 10:38 PM zhoumin wrote:
>
> Hi Patrick,
>
> Thanks for giving the link of commit `a6c3ec342ee1`.
>
> However I cannot checkout this commit in the next-net repository because
> the commit ID is not exist in the history of next-net repository. Could
> you find it?
>
> It seem
Rerunning the CI Test for Broadcom Performance, which appears to be a
false failure.
On Thu, Jun 27, 2024 at 4:52 PM Patrick Robb wrote:
> #
> Minutes
>
> =
> General Announcements
> * DPDK Summit in Montreal will be Septem
July 18, 2024
#
Attendees
* Patrick Robb
* juraj.lin...@pantheon.tech
* paul.szczepa...@arm.com
* Jeremy Spewock
* Dean Marx
* Nicholas Pratte
* Alex Chapman
#
July 25, 2024
Attendees
1. Patrick Robb
2. Jeremy Spewock
3. Juraj Linkeš
4. Aaron Conole
5. Adam Hassick
6. Dean Marx
7. Luca Vizzarro
8. Manit Mahajan
9. Paul Szczepanek
10. Tomas Durovec
Hi Stephen,
This is a UNH Lab system.
We review our systems for updates once every 4 months. The idea is we
do it early in each DPDK release's development cycle. So, we update
Dockerfiles (for container environments), we apply updates where
needed to persistent systems (for VMs, or baremetal serv
this also raises the question of whether the DPDK docs for the
windows mingw64 compile process should be updated to point to
winlibs.com instead of sourceforge.net (only has the source code).
https://doc.dpdk.org/guides/windows_gsg/build_dpdk.html#option-2-mingw-w64-toolchain
On Thu, Jul 25, 202
August 1, 2024
#
Attendees
* Patrick Robb
* Jeremy Spewock
* Nicholas Pratte
* Juraj Linkeš
* Alex Chapman
* Luca Vizzarro
#
Minutes
I saw there was one fail for this series for the Marvell MVNETA container.
I thought I should also mention that the build did fail when our
automation tried to run DTS on the Octeon CN10K DPU (which is also
Marvell). So, that is why you won't get a report for the CN10K DTS
results.
Let me know if
Thanks I will merge the change disabling ABI checks at UNH at start of
day tomorrow.
On Thu, Aug 8, 2024 at 8:56 AM David Marchand wrote:
>
> On Thu, Aug 8, 2024 at 2:00 PM Thomas Monjalon wrote:
> >
> > 08/08/2024 10:03, David Marchand:
> > > Start a new release cycle with empty release notes.
#
August 8, 2024
Attendees
1. Patrick Robb
2. Juraj Linkeš
3. Aaron Conole
4. Alex Chapman
5. Dean Marx
6. Jeremy Spewock
7. Luca Vizzarro
8. Nicholas Pratte
9. Paul Szczepanek
10. Manit Mahajan
Recheck-request: iol-marvell-Functional
Putting in a retest for this.
#
August 15, 2024
Attendees
* Patrick Robb
* Jeremy Spewock
* Alex Chapman
* Juraj Linkeš
* Tomas Durovec
* Dean Marx
* Luca Vizzarro
* Paul Szczepanek
* Nicholas Pratte
#
August 22, 2024
Attendees
1. Patrick Robb
2. Tomas Durovec
3. Dean Marx
4. Luca Vizzarro
5. Jeremy Spewock
6. Ali Alnubani
7. Juraj Linkeš
8. Paul Szczepanek
Recheck-request: iol-marvell-Functional
On Fri, Aug 23, 2024 at 7:56 AM Soumyadeep Hore
wrote:
>
> In E830 adapters, PHY timestamp for Tx packets should be read once
> the ready status of PHY timestamp registers is 1.
>
> Fixes: 881169950d80 ("net/ice/base: implement initial PTP support for E830"
Recheck-request: iol-marvell-Functional
On Fri, Aug 23, 2024 at 6:51 AM Soumyadeep Hore
wrote:
>
> Updating the latest shared code patches to ICE base driver.
>
> ---
> v3:
> - Addressed comments givn by reviewer
> ---
> v2:
> - Addressed comments given by reviewer
> - Corrected errors in Camel C
ork/remote_session/remote_session.py
>> create mode 100644 dts/framework/test_result.py
>> create mode 100644 dts/framework/test_suite.py
>> create mode 100644 dts/framework/testbed_model/dpdk.py
>> create mode 100644 dts/framework/testbed_model/hw/__init__.py
>> create mode 100644 dts/framework/testbed_model/hw/cpu.py
>> create mode 100644 dts/framework/testbed_model/hw/virtual_device.py
>> create mode 100644 dts/framework/testbed_model/sut_node.py
>> create mode 100644 dts/test_plans/hello_world_test_plan.rst
>> create mode 100644 dts/tests/TestSuite_hello_world.py
>>
>> --
>> 2.30.2
>>
>>
Tested-by: Patrick Robb
--
Patrick Robb
Technical Service Manager
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
www.iol.unh.edu
lume, which is essentially a
> > symlink from the host to the container.
> > +This enables you to edit and run inside the container and then delete
> > +the container when you are done, keeping your work.
> > +
> > +```shell
> > +docker build --target dev -t dpdk-dts .
> > +docker run -v $(pwd)/..:/dpdk -it dpdk-dts bash $ poetry install $
> > +poetry shell ```
> > +
> > +### Vim/Emacs
> > +Any editor in the ubuntu repos should be easy to use, with vim and
> > +emacs already installed. You can add your normal config files as a
> > +volume, enabling you to use your preferred settings.
> > +
> > +```shell
> > +docker run -v ${HOME}/.vimrc:/root/.vimrc -v $(pwd)/..:/dpdk -it
> > +dpdk-dts bash ```
> > +
> > +### Visual Studio Code
> > +VSCode has first-class support for developing with containers. You may
> > +need to run the non-docker setup commands in the integrated terminal.
> > +DTS contains a .devcontainer config, so if you open the folder in
> > +vscode it should prompt you to use the dev container assuming you have
> > +the plugin installed. Please refer to [VS Development Containers
> > +Docs](https://code.visualstudio.com/docs/remote/containers)
> > +to set it all up.
> > +
> > +### Other
> > +Searching for '$IDE dev containers' will probably lead you in the right
> > direction.
> > --
> > 2.30.2
>
> Tested-by: Patrick Robb
--
Patrick Robb
Technical Service Manager
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
www.iol.unh.edu
tested algorithms*:
-
RSA
-
ECDSA
--
Patrick Robb
Technical Service Manager
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
www.iol.unh.edu
> > if (add_guest_pages(dev, region, alignment) < 0) {
> > > @@ -1535,7 +1574,6 @@ inflight_mem_alloc(struct virtio_net *dev, const
> char *name, size_t size, int *f
> > > return NULL;
> > > }
> > >
> > > - mem_set_dump(ptr, size, false);
> > > *fd = mfd;
> > > return ptr;
> > > }
> > > @@ -1566,6 +1604,7 @@ vhost_user_get_inflight_fd(struct virtio_net
> **pdev,
> > > uint64_t pervq_inflight_size, mmap_size;
> > > uint16_t num_queues, queue_size;
> > > struct virtio_net *dev = *pdev;
> > > + uint64_t alignment;
> > > int fd, i, j;
> > > int numa_node = SOCKET_ID_ANY;
> > > void *addr;
> > > @@ -1628,6 +1667,8 @@ vhost_user_get_inflight_fd(struct virtio_net
> **pdev,
> > > dev->inflight_info->fd = -1;
> > > }
> > >
> > > + alignment = get_blk_size(fd);
> > > + mem_set_dump(addr, mmap_size, false, alignment);
> > > dev->inflight_info->addr = addr;
> > > dev->inflight_info->size = ctx->msg.payload.inflight.mmap_size =
> mmap_size;
> > > dev->inflight_info->fd = ctx->fds[0] = fd;
> > > @@ -1744,10 +1785,10 @@ vhost_user_set_inflight_fd(struct virtio_net
> **pdev,
> > > dev->inflight_info->fd = -1;
> > > }
> > >
> > > - mem_set_dump(addr, mmap_size, false);
> > > dev->inflight_info->fd = fd;
> > > dev->inflight_info->addr = addr;
> > > dev->inflight_info->size = mmap_size;
> > > + mem_set_dump(addr, mmap_size, false, get_blk_size(fd));
> > >
> > > for (i = 0; i < num_queues; i++) {
> > > vq = dev->virtqueue[i];
> > > @@ -2242,6 +2283,7 @@ vhost_user_set_log_base(struct virtio_net **pdev,
> > > struct virtio_net *dev = *pdev;
> > > int fd = ctx->fds[0];
> > > uint64_t size, off;
> > > + uint64_t alignment;
> > > void *addr;
> > > uint32_t i;
> > >
> > > @@ -2280,6 +2322,7 @@ vhost_user_set_log_base(struct virtio_net **pdev,
> > >* fail when offset is not page size aligned.
> > >*/
> > > addr = mmap(0, size + off, PROT_READ | PROT_WRITE, MAP_SHARED,
> fd, 0);
> > > + alignment = get_blk_size(fd);
> > > close(fd);
> > > if (addr == MAP_FAILED) {
> > > VHOST_LOG_CONFIG(dev->ifname, ERR, "mmap log base
> failed!\n");
> > > @@ -2296,7 +2339,7 @@ vhost_user_set_log_base(struct virtio_net **pdev,
> > > dev->log_addr = (uint64_t)(uintptr_t)addr;
> > > dev->log_base = dev->log_addr + off;
> > > dev->log_size = size;
> > > - mem_set_dump(addr, size, false);
> > > + mem_set_dump(addr, size + off, false, alignment);
> > >
> > > for (i = 0; i < dev->nr_vring; i++) {
> > > struct vhost_virtqueue *vq = dev->virtqueue[i];
> >
>
>
--
Patrick Robb
Technical Service Manager
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
www.iol.unh.edu
patch series
may resolve our ciphertext issue with AES-GCM test vector and more issues
with the sample app. So - looking forward to seeing a patch like this being
merged when stable!
Best,
Patrick Robb
On Tue, Feb 28, 2023 at 2:39 AM Akhil Goyal wrote:
> Hi Gowrishan
AfWxebW0mSomWcCW-0s59wZNJ7QED4-Tjcs&e=>.
> We reported a warn because it failed on the compilation stage (as opposed
> to a failure of the actual sample app run).
>
>
>
> On the other hand, we are excited to see this patch again with the
> compilation part resolved. I se
Tested-by: Patrick Robb
On Fri, Mar 3, 2023 at 5:25 AM Juraj Linkeš
wrote:
> Document how to configure and run DTS.
> Also add documentation related to new features: SUT setup and a brief
> test suite implementation cookbook.
>
> Signed-off-by: Juraj Linkeš
> ---
> doc
Recheck-request: iol-intel-Functional
I saw this failed in CI testing for the DTS mtu_update test but suspect it
was an infra failure as it happened across 3 distinct patches in a short
span of time. So, triggering a retest.
Recheck-request: iol-intel-Functional
I saw this failed in CI testing for the DTS MTU_Update test but suspect it
was an infra failure as it happened across 3 distinct patches in a short
span of time. So, triggering a retest.
Recheck-request: iol-intel-Functional
I saw this failed in CI testing for the DTS MTU_Update test but suspect it
was an infra failure as it happened across 3 distinct patches in a short
span of time. So, triggering a retest.
Hi Aaron/Cristian,
On Wed, Feb 14, 2024 at 11:25 AM Aaron Conole wrote:
> Ferruh Yigit writes:
>
> > On 2/13/2024 5:38 PM, Cristian Dumitrescu wrote:
> >> When rte_log.h was moved to a new directory, the include path was not
> >> updated for the generated C code produced by the pipeline library
On Wed, Feb 14, 2024 at 3:00 PM Dumitrescu, Cristian <
cristian.dumitre...@intel.com> wrote:
>
>
> [Cristian]
> Yes, you are right, we do have a DTS test suite for the pipeline library.
>
> It would be great to run it automatically as part of the CI testing. Just
> a word of caution though: I am n
February 14, 2024
#
Attendees
* Patrick Robb
* Juraj Linkeš
* Thomas Monjalon
* Gregory Etelson
* Juraj Linkes
* Luca Vizzarro
* Nicholas Pratte
#
Agenda
Hello all,
As discussed in the previous CI testing meeting, it will be advantageous
for us to shift the (every other week) DPDK CI meetings forward or
backwards 1 week to get it onto a different cadence.
That will allow us to have the DTS meetings 1 week, and the CI meetings on
the off week, inst
Hi,
This is finalized. The next CI meeting will be next Thursday. Then we go
back to every other week.
On Wed, Feb 14, 2024 at 4:20 PM Patrick Robb wrote:
> Hello all,
>
> As discussed in the previous CI testing meeting, it will be advantageous
> for us to shift the (every other w
+Gao, DaxueX +Mcnamara, John
Hello,
As you say the Community Lab dropped main and next-* testing for RHEL7 when
the requirement for a C11 compliant compiler was added last year, so we
should already be good to go. We don't have any centos7 testing (centos8
was the first centos introduced for te
d you have time to check the Unit Test design ?
> Do you think it can be used for short functional DTS tests ?
>
> Regards,
> Gregory
>
> --
> *From:* Gregory Etelson
> *Sent:* Wednesday, January 31, 2024 09:43
> *To:* Patrick Robb
Hi all,
I want to poll the CI group and dev community about a proposed feature
addition to the CI retest request framework. Currently, you can respond to
a patchseries or patch email, requesting a retest like so:
Recheck-request: iol-compile-amd64-testing, iol-unit-amd64-testing
Labs who have ad
On Tue, Feb 20, 2024 at 1:12 PM Aaron Conole wrote:
>
> Why not something like:
>
> Recheck-request: [attribute-list],[test-list]...
>
> For example, then we can do:
>
> Recheck-request: rebase=[identifier],
>
> where identifier is a branch specifier (or the word 'latest')?
>
I hadn't thought
Tested-by: Patrick Robb
I ran this testsuite with a bnxt_en NIC at the Community Lab.
I also spoke with Jeremy about the state of this patch today. He wants to
add a second testcase to the suite for testing the scattered packets
hardware offload (--enable-scatter flag in testpmd). But, he still
Tested-by: Patrick Robb
The approach for mounting in ssh keys and managing the test engine
environment has been agreed upon by the CI group, and this patch has been
tested by a few people at the Community Lab. I believe it is ready to be
merged.
On Tue, Jan 16, 2024 at 2:18 PM wrote:
> F
On Tue, Jun 20, 2023 at 5:44 AM Fangming Fang wrote:
> v1.4 release on the arm repo breaks DPDK
> We have reverted the Arm library version to 1.3.0 to work around this
> issue according to Pablo's suggestion. The library fixing this issue is
> tagged as SECLIB-IPSEC-2023.06.20.
>
> Thanks,
> Fang
gt;
> > On Feb 20, 2024, at 11:01 PM, Patrick Robb wrote:
> >
> >
> >
> > On Tue, Jun 20, 2023 at 5:44 AM Fangming Fang
> wrote:
> > v1.4 release on the arm repo breaks DPDK
> > We have reverted the Arm library version to 1.3.0 to work around this
&g
On Wed, Feb 21, 2024 at 4:50 AM Power, Ciara wrote:
>
> Hi folks,
>
> We had based the ipsec-mb version bump to 1.4 on both intel ipsec-mb and
> arm ipsec-mb supporting that version, so both could still use the Ipsec-mb
> SW PMDs.
> I based the arm support from the repo main branch (
> https://gi
https://patchwork.dpdk.org/project/dpdk/patch/20240208171330.31139-8-ajit.khapa...@broadcom.com/
Hi Ajit,
So you know, this series did fail in CI testing, and now that it is merged
to main, all patchseries are failing DTS at EAL. Performance testing is
also offline for the same reason.
I will ru
February 22, 2024
#
Attendees
1. Patrick Robb
2. Ali Alnubani
3. Paul Szczepanek
4. Juraj Linkeš
5. Luca Vizzarro
#
Minutes
Recheck-request: iol-broadcom-Performance
This patch should not fail a performance test in CI - checking with a rerun
now.
On Mon, Feb 26, 2024 at 5:25 AM Radu Nicolau wrote:
> There are use cases where a SA should be able to use different cryptodevs
> on
> different lcores, for example there c
Recheck-request: iol-unit-arm64-testing
This ran before we had swapped out the old arm v1.2 ipsec container for our
new arm v1.4 ipsec container. We have now made that change, so this retest
should report a pass. Sorry for the inconvenience.
On Fri, Feb 23, 2024 at 7:21 AM Sivaramakrishnan Venka
On Mon, Feb 26, 2024 at 6:24 PM Wathsala Wathawana Vithanage <
wathsala.vithan...@arm.com> wrote:
> Hi Patrick,
> > I tried mainline earlier today it compiles and links fine. However,
> build failed on
> > v1.4. We are working on tagging the mainline, until then please continue
> > working on main
Acked-by: Patrick Robb
The Community Lab had an infra failure this morning and some patches
including yours were affected with false failures. The issue is now
resolved and we are rerunning the tests in question for all patches
submitted today.
On Fri, Mar 1, 2024 at 7:43 AM Suanming Mou wrote:
> Currently, for multi-
The Community CI Testing Lab had an infra failure this morning and some
patches including yours were affected with false failures. The issue is now
resolved and we are rerunning the tests in question for all patches
submitted today.
On Fri, Mar 1, 2024 at 7:31 AM Suanming Mou wrote:
> This adds
The Community CI Testing Lab had an infra failure this morning and some
patches including yours were affected with false failures. The issue is now
resolved and we are rerunning the tests in question for all patches
submitted today.
On Fri, Mar 1, 2024 at 5:55 AM Juraj Linkeš
wrote:
> We current
The Community CI Testing Lab had an infra failure this morning and some
patches including yours were affected with false failures. The issue is now
resolved and we are rerunning the tests in question for all patches
submitted today.
On Fri, Mar 1, 2024 at 6:16 AM Morten Brørup
wrote:
> > From: K
The Community CI Testing Lab had an infra failure this morning and some
patches including yours were affected with false failures. The issue is now
resolved and we are rerunning the tests in question for all patches
submitted today.
On Fri, Mar 1, 2024 at 5:25 AM Bruce Richardson
wrote:
> On Fri
The Community CI Testing Lab had an infra failure this morning and some
patches including yours were affected with false failures. The issue is now
resolved and we are rerunning the tests in question for all patches
submitted today.
On Fri, Mar 1, 2024 at 5:11 AM Mingjin Ye wrote:
> Implemented
The Community CI Testing Lab had an infra failure this morning and some
patches including yours were affected with false failures. The issue is now
resolved and we are rerunning the tests in question for all patches
submitted today.
On Fri, Mar 1, 2024 at 3:46 AM Shun Hao wrote:
> Currently a me
Hi all,
As some of you know from discussions at DPDK CI meetings, Adam from UNH is
writing a script which leverages git-pw, and takes as arguments a patch
series patchwork id, patchwork project, and pw token, and produces a
project artifact for CI testing purposes. Starting in January we will use
On Thu, Jan 11, 2024 at 4:18 AM Morten Brørup
wrote:
>
> I wonder if any automated tests are using this specific kernel version, or
> if we are only testing using the distros' native kernels. @Aaron?
>
For UNH, we generally run from the distros' native kernels. Any exceptions
are not for testing
On Thu, Jan 11, 2024 at 2:27 PM Morten Brørup
wrote:
> *From:* Patrick Robb [mailto:pr...@iol.unh.edu]
> *Sent:* Thursday, 11 January 2024 20.02
>
>
>
> On Thu, Jan 11, 2024 at 4:18 AM Morten Brørup
> wrote:
>
>
> I wonder if any automated tests are using this sp
On Tue, Jan 16, 2024 at 11:45 AM Honnappa Nagarahalli <
honnappa.nagaraha...@arm.com> wrote:
>
> 3. How well does DPDK run on Hyperscaler environments?
> - Can UNH take the task of running DPDK on Hyperscaler environments? UNH
> seems to have lot of things already.
>
Sorry, I could not make techb
=
General Announcements
* First 2024 DTS WG meeting was held yesterday, and the minutes are here:
https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp=sharing
* Patrick Robb will publish the
I forgot to CC the dev mailing list
-- Forwarded message -
From: Patrick Robb
Date: Thu, Jan 18, 2024 at 2:52 PM
Subject: DTS WG Meeting Minutes - January 17, 2024
To:
Cc: , NBU-Contact-Thomas Monjalon (EXTERNAL) <
tho...@monjalon.net>, Juraj Linkeš
January 17
gt; >
>> > > However, YAML is supposed to be easy to read and understand. Is it
>> just a
>> > matter for getting used to it?
>> > >
>> >
>> > I selected YAML for 2 reasons:
>> >* Plain and intuitive YAML format minimized t
ards,
> Gregory
> --
> *From:* Jeremy Spewock
> *Sent:* Tuesday, January 23, 2024 20:26
> *To:* NBU-Contact-Thomas Monjalon (EXTERNAL)
> *Cc:* Honnappa Nagarahalli ; Gregory
> Etelson ; Juraj Linkeš ;
> Paul Szczepanek ; Yoan Picchi <
> yo
January 31, 2024
#
Attendees
* Patrick Robb
* Juraj Linkeš
* Paul Szczepanek
* Jeremy Spewock
* Luca Vizzarro
* Thomas Monjalon
#
Agenda
* Additions to the
February 1, 2024
#
Attendees
1. Patrick Robb
2. Paul Szczepanek
3. Thomas Monjalon
4. Juraj Linkes
5. Ali Alnubani
6. Aaron Conole
#
Minutes
Reviewed-by: Patrick Robb
Reviewed-by: Patrick Robb
Recheck-request: github-robot
Hi Ali,
Wathsala reached out asking how the checkpatch CI check can be updated so
that this series passes checkpatch.
If building the dictionary is a 1 time operation for you, you may have to
apply this patch and re-run devtools/build-dict.sh so that the new
dictionary is in place for a V3 of thi
#
Attendees
* Patrick Robb
* Juraj Linkeš
* Paul Szczepanek
* Luca Vizzarro
* Nicholas Pratte
#
Minutes
Recheck-request: iol-compile-amd64-testing
The DPDK Community Lab updated to the latest Alpine image yesterday, which
resulted in all Alpine builds failing. The failure is unrelated to your
patch, and this recheck should remove the fail on Patchwork, as we have
disabled Alpine testing for now.
Recheck-request: iol-compile-amd64-testing
The DPDK Community Lab updated to the latest Alpine image yesterday, which
resulted in all Alpine builds failing. The failure is unrelated to your
patch, and this recheck should remove the fail on Patchwork, as we have
disabled Alpine testing for now.
Recheck-request: iol-compile-amd64-testing
The DPDK Community Lab updated to the latest Alpine image yesterday, which
resulted in all Alpine builds failing. The failure is unrelated to your
patch, and this recheck should remove the fail on Patchwork, as we have
disabled Alpine testing for now.
Recheck-request: iol-compile-amd64-testing
The DPDK Community Lab updated to the latest Alpine image yesterday, which
resulted in all Alpine builds failing. The failure is unrelated to your
patch, and this recheck should remove the fail on Patchwork, as we have
disabled Alpine testing for now.
Recheck-request: iol-compile-amd64-testing
The DPDK Community Lab updated to the latest Alpine image yesterday, which
resulted in all Alpine builds failing. The failure is unrelated to your
patch, and this recheck should remove the fail on Patchwork, as we have
disabled Alpine testing for now.
Recheck-request: iol-compile-amd64-testing
The DPDK Community Lab updated to the latest Alpine image yesterday, which
resulted in all Alpine builds failing. The failure is unrelated to your
patch, and this recheck should remove the fail on Patchwork, as we have
disabled Alpine testing for now.
Recheck-request: iol-compile-amd64-testing
The DPDK Community Lab updated to the latest Alpine image yesterday, which
resulted in all Alpine builds failing. The failure is unrelated to your
patch, and this recheck should remove the fail on Patchwork, as we have
disabled Alpine testing for now.
Recheck-request: iol-compile-amd64-testing
The DPDK Community Lab updated to the latest Alpine image yesterday, which
resulted in all Alpine builds failing. The failure is unrelated to your
patch, and this recheck should remove the fail on Patchwork, as we have
disabled Alpine testing for now.
Recheck-request: iol-compile-amd64-testing
The DPDK Community Lab updated to the latest Alpine image yesterday, which
resulted in all Alpine builds failing. The failure is unrelated to your
patch, and this recheck should remove the fail on Patchwork, as we have
disabled Alpine testing for now.
Recheck-request: iol-compile-amd64-testing
The DPDK Community Lab updated to the latest Alpine image yesterday, which
resulted in all Alpine builds failing. The failure is unrelated to your
patch, and this recheck should remove the fail on Patchwork, as we have
disabled Alpine testing for now.
Recheck-request: iol-compile-amd64-testing
The DPDK Community Lab updated to the latest Alpine image yesterday, which
resulted in all Alpine builds failing. The failure is unrelated to your
patch, and this recheck should remove the fail on Patchwork, as we have
disabled Alpine testing for now.
Recheck-request: iol-compile-amd64-testing
The DPDK Community Lab updated to the latest Alpine image yesterday, which
resulted in all Alpine builds failing. The failure is unrelated to your
patch, and this recheck should remove the fail on Patchwork, as we have
disabled Alpine testing for now.
On Mon, Apr 29, 2024 at 6:01 AM David Marchand
wrote:
> Following an upgrade of musl, pread64/pwrite64 wrappers are not provided
> anymore. Switch to POSIX pread/pwrite.
>
> Bugzilla ID: 1422
> Cc: sta...@dpdk.org
>
> Signed-off-by: David Marchand
>
>
Tested-by: Patri
On Mon, Apr 29, 2024 at 9:49 AM Jeremy Spewock wrote:
>
> > The patchset contains the .rst sources which Sphinx uses to generate the
> > html pages. These were first generated with the sphinx-apidoc utility
> > and modified to provide a better look. The documentation just doesn't
> > look that g
On Sun, Apr 28, 2024 at 3:46 AM Mattias Rönnblom
wrote:
> It would be great if the unit test suite (app/test/*) was compiled (and
> run) using a C++ (C++11) compiler as well. At least, if such is available.
>
Sure, the UNH Lab can try this.
>
> With the current state of affairs, header file ma
On Tue, Apr 30, 2024 at 4:13 PM Mattias Rönnblom
wrote:
> On 2024-04-30 15:52, Patrick Robb wrote:
> >
> >
> > On Sun, Apr 28, 2024 at 3:46 AM Mattias Rönnblom > <mailto:hof...@lysator.liu.se>> wrote:
> >
> > It would be great if the uni
#
May 2, 2024
Attendees
1. Patrick Robb
2. Juraj Linkeš
3. Aaron Conole
4. Paul Szczepanek
5. Luca Vizzarro
#
Minutes
Hi DPDK Developers,
I wanted to announce to the mailing lists that the UNH Community Lab
recently rolled out a new page on our dashboard where you can find
code coverage reports for DPDK unit tests.
https://lab.dpdk.org/results/dashboard/code-coverage
It provides some unit test code coverage rep
Recheck-request: iol-broadcom-Performance
On Mon, May 6, 2024 at 1:58 PM Tyler Retzlaff
wrote:
>
> This series converts all non-generic built atomics to use the rte_atomic
> macros that allow optional enablement of standard C11 atomics.
>
> Use of generic atomics for non-scalar types are not conv
When we sent this out originally we missed some patches Luca Vizzarro
has been working on for this release, so here is an updated version.
Thanks Luca.
1) Write ethdev testsuites:
Jumboframes:
https://git.dpdk.org/tools/dts/tree/test_plans/jumboframes_test_plan.rst
Mac Filter:
https://git.dpdk.
1 - 100 of 521 matches
Mail list logo
