DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/eventdev Bug 1607] cnkx eventdev drivers take too long to compile
Date: Thu, 26 Dec 2024 18:48:42 +0000	[thread overview]
Message-ID: <bug-1607-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 839 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1607

            Bug ID: 1607
           Summary: cnkx eventdev drivers take too long to compile
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: eventdev
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

I am doing test builds on Raspberry Pi 5.
Most of the DPDK builds quite rapidly but the CNXK eventdev PMD had lots and
lots of little files which are all clones of the same thing for different
sizes.
It can add many 15 minutes or more to the build.

There must be a better way.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 2713 bytes --]

                 reply	other threads:[~2024-12-26 18:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1607-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).