On Thu, Jan 14, 2021 at 4:03 PM Anatoly Burakov
wrote:
>
> When we're attaching fbarrays in secondary processes, we check for
> whether the intended memory address for the fbarray is already in use by
> some other, local fbarray. However, the check for end-overlap (i.e. to
> see if our memory area
Tested-by: Peng, ZhihongX
Regards,
Peng,Zhihong
-Original Message-
From: dev On Behalf Of Anatoly Burakov
Sent: Thursday, January 14, 2021 11:03 PM
To: dev@dpdk.org
Cc: sta...@dpdk.org
Subject: [dpdk-dev] [PATCH] fbarray: fix incorrect overlap check
When we're attaching fbarra
When we're attaching fbarrays in secondary processes, we check for
whether the intended memory address for the fbarray is already in use by
some other, local fbarray. However, the check for end-overlap (i.e. to
see if our memory area's end overlaps with some other fbarray) is
incorrectly counting e
3 matches
Mail list logo