DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luca Boccassi <luca.boccassi@gmail.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: stable@dpdk.org, dev@dpdk.org, andrew.rybchenko@oktetlabs.ru
Subject: Re: 20.11.7 patches review and test
Date: Mon, 28 Nov 2022 11:55:26 +0000	[thread overview]
Message-ID: <CAMw=ZnTH6DOxvobXzpe02OGgTU9kQJxGqpdYftu6U64WkMPw_A@mail.gmail.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D8751A@smartserver.smartshare.dk>

On Mon, 28 Nov 2022 at 11:35, Morten Brørup <mb@smartsharesystems.com> wrote:
>
> +CC Andrew Rybchenko as co-signer on the mempool patch in mainline.
>
> > From: luca.boccassi@gmail.com [mailto:luca.boccassi@gmail.com]
> > Sent: Monday, 28 November 2022 11.53
> >
> > Hi all,
> >
> > Here is a list of patches targeted for stable release 20.11.7.
> >
> > The planned date for the final release is the 12th of December.
> >
> > Please help with testing and validation of your use cases and report
> > any issues/results with reply-all to this mail. For the final release
> > the fixes and reported validations will be added to the release notes.
> >
> > A release candidate tarball can be found at:
> >
> >     https://dpdk.org/browse/dpdk-stable/tag/?id=v20.11.7-rc1
> >
> > These patches are located at branch 20.11 of dpdk-stable repo:
> >     https://dpdk.org/browse/dpdk-stable/
>
> The link with pre-selected branch seems to be:
> https://git.dpdk.org/dpdk-stable/?h=20.11
>
> [...]
>
> > Morten Brørup (2):
> >       eal/x86: add 256 bytes copy for AVX2
>
> LGTM.
>
> >       mempool: fix get objects from mempool with cache
>
> Reviewed stable release patch [1], comparing it to the accepted mainline patch [2].
>
> [1]: https://git.dpdk.org/dpdk-stable/commit/?h=20.11&id=26cb4c81b552594292f7c744afb904f01700dfe8
> [2]: https://patchwork.dpdk.org/project/dpdk/patch/20221007104450.2567961-1-andrew.rybchenko@oktetlabs.ru/
>
> This is not correct:
> +               __MEMPOOL_STAT_ADD(mp, get_success_bulk, 1);
> +               __MEMPOOL_STAT_ADD(mp, get_success_objs, n);
>
> The old macro did more, so it should be:
> +               __MEMPOOL_STAT_ADD(mp, get_success, n);
>
> This is only visible if built with RTE_LIBRTE_MEMPOOL_DEBUG.
>
> Besides that, it looks perfectly good to me.

Can you test a patch and send it?

Kind regards,
Luca Boccassi

  reply	other threads:[~2022-11-28 11:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28 10:52 luca.boccassi
2022-11-28 11:35 ` Morten Brørup
2022-11-28 11:55   ` Luca Boccassi [this message]
2022-11-28 12:07     ` Morten Brørup
2023-04-11  7:22       ` Morten Brørup
2023-04-11  9:58         ` Luca Boccassi
2022-12-07 10:21 ` Jiang, YuX
2022-12-09  9:24   ` YangHang Liu
2022-12-09  9:50     ` Luca Boccassi
2022-12-09  9:49   ` Luca Boccassi
2022-12-12 20:01     ` Luca Boccassi
2022-12-13  9:05     ` Jiang, YuX
2022-12-13 10:12       ` Luca Boccassi
2022-12-11 16:15 ` Ali Alnubani
2022-12-12 20:00   ` Luca Boccassi

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='CAMw=ZnTH6DOxvobXzpe02OGgTU9kQJxGqpdYftu6U64WkMPw_A@mail.gmail.com' \
    --to=luca.boccassi@gmail.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=stable@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).