From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] fbarray: add internal tailq for mapped areas
Date: Thu, 28 Mar 2019 21:44:32 +0100 [thread overview]
Message-ID: <1848003.AzJ49HI9Wz@xps> (raw)
In-Reply-To: <d43eba58247bbd4a5c3eb1eb36cd728338daf364.1551201154.git.anatoly.burakov@intel.com>
26/02/2019 18:13, Anatoly Burakov:
> Currently, there are numerous reliability issues with fbarray,
> such as:
> - There is no way to prevent attaching to overlapping memory
> areas
> - There is no way to prevent double-detach
> - Failed destroy leaves fbarray in an invalid state (fbarray
> itself is valid, but its backing memory area is already
> detached)
>
> In addition, on FreeBSD, doing mmap() on a file descriptor
> does not keep the lock, so we also need to store the fd
> in order to keep the lock.
>
> This patch improves upon fbarray to address both of these
> issues by adding an internal tailq to track allocated areas
> and their respective file descriptors.
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied, thanks
next prev parent reply other threads:[~2019-03-28 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 17:13 [PATCH] fbarray: add internal tailq for mapped areas Anatoly Burakov
2019-03-28 20:44 ` Thomas Monjalon [this message]
2019-03-29 5:22 ` Stojaczyk, Dariusz
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=1848003.AzJ49HI9Wz@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--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 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.