From: Thomas Monjalon <thomas@monjalon.net>
To: Raslan Darawsheh <rasland@nvidia.com>
Cc: dev@dpdk.org, ggribbon@nvidia.com, stable@dpdk.org,
Ori Kam <orika@nvidia.com>
Subject: Re: [PATCH] app/regex: fix mbuf size for multi segemnt buffers
Date: Tue, 05 Jul 2022 22:20:30 +0200 [thread overview]
Message-ID: <7289277.60r6i4UCyb@thomas> (raw)
In-Reply-To: <20220705080917.13784-1-rasland@nvidia.com>
05/07/2022 10:09, Raslan Darawsheh:
> When allocating multi segmented buffers, and in case there is
> a remainder in total buf len, the actual job len might be more
> than expected job_len.
>
> This adds additional space in the mbuf in the multi seg case,
> to allow the remaining memory to be stored in one segment.
>
> Fixes: c1d1b94eec58 ("app/regex: fix number of matches")
> Cc: ggribbon@nvidia.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Raslan Darawsheh <rasland@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
Applied (with fixed typo in title), thanks.
prev parent reply other threads:[~2022-07-05 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 8:09 [PATCH] app/regex: fix mbuf size for multi segemnt buffers Raslan Darawsheh
2022-07-05 20:20 ` 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=7289277.60r6i4UCyb@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ggribbon@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.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 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.