From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Avi Kivity <avi@cloudius-systems.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] eal/persistent: new library to hold memory region after program exit
Date: Mon, 06 Jul 2015 16:41:16 +0200 [thread overview]
Message-ID: <3774699.APpBeIyZp2@xps13> (raw)
In-Reply-To: <559A91DD.9020309@cloudius-systems.com>
2015-07-06 17:34, Avi Kivity:
> On 07/06/2015 04:28 PM, leeopop wrote:
> > Some NICs use host memory region as their scratch area.
> > When DPDK user applications terminate, all the memory regions are lost,
> > re-initialized (memzone), which causes HW faults.
> > This libraray maintains shared memory regions that is persistent across
> > multiple execution and termination of user level applications.
> > It also manages physically contiguous memory regions.
> >
> > Signed-off-by: leeopop <dlrmsghd@gmail.com>
> >
>
> Does dpdk accept anonymous signoffs?
>
> DCO usually requires a real name.
Exact. We follow Linux guidelines for DCO:
http://dpdk.org/dev#send
next prev parent reply other threads:[~2015-07-06 14:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 13:28 [dpdk-dev] [PATCH 0/2] Native uio-based PMD for Mellanox ConnectX-3 devices leeopop
2015-07-06 13:28 ` [dpdk-dev] [PATCH 1/2] eal/persistent: new library to hold memory region after program exit leeopop
2015-07-06 14:34 ` Avi Kivity
2015-07-06 14:41 ` Thomas Monjalon [this message]
2015-07-06 19:19 ` Stephen Hemminger
2015-07-06 13:28 ` [dpdk-dev] [PATCH 2/2] mlnx_uio: new poll mode driver leeopop
2015-07-06 14:17 ` [dpdk-dev] [PATCH 0/2] Native uio-based PMD for Mellanox ConnectX-3 devices Thomas Monjalon
2015-07-06 15:57 ` Keunhong Lee
2015-07-06 16:14 ` Thomas Monjalon
2015-07-06 17:55 ` Keunhong Lee
2015-07-07 6:50 ` Olga Shern
2015-07-07 7:02 ` Pavel Odintsov
2015-07-07 9:18 ` Olga Shern
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=3774699.APpBeIyZp2@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=avi@cloudius-systems.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 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).