All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Luca Boccassi <bluca@debian.org>,
	"Ji, Kai" <kai.ji@intel.com>
Subject: Re: [PATCH] test/memcpy: reduce alignment offset coverage to fix timeout
Date: Tue, 17 Mar 2026 18:01:16 +0100	[thread overview]
Message-ID: <3426001.VqM8IeB0Os@thomas> (raw)
In-Reply-To: <DS0PR11MB74580F7BC395E2044587F9628146A@DS0PR11MB7458.namprd11.prod.outlook.com>

> > The memcpy test sweeps all 32x32 src/dst alignment offset pairs which
> > causes it to timeout on slow emulated 32-bit build environments [1].
> > 
> > Replace with a curated set of 7 offsets {0, 1, 7, 15, 16, 17, 31}
> > that cover the interesting alignment boundaries. This reduces the
> > iterations from 38912 to 1862 while covering the same code paths.
> > 
> > [1]
> > https://build.opensuse.org/package/live_build_log/home:bluca:dpdk/dpdk/De
> > bian_Testing/i586
> > 
> > Reported-by: Luca Boccassi <bluca@debian.org>
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> 
> 10/03/2026 18:04, Ji, Kai:
> LGTM,
> 
> I'm not AVX-512 expert, but I think AVX-512 might expect  64-bytes alignment,.
> As the original  ALIGNMENT_UNIT is 32, so I think the selection of offsets is no problem.
> Maybe remove AVX-512 from the comments ?

Applied with AVX512 removed from the comment, thanks.



      reply	other threads:[~2026-03-17 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 16:48 [PATCH] test/memcpy: reduce alignment offset coverage to fix timeout Stephen Hemminger
2026-03-10 17:04 ` Ji, Kai
2026-03-17 17:01   ` Thomas Monjalon [this message]

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=3426001.VqM8IeB0Os@thomas \
    --to=thomas@monjalon.net \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.com \
    --cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.