From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: dev@dpdk.org, David Marchand <david.marchand@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] eal: remove single file segments related code
Date: Fri, 23 Sep 2016 10:50:06 +0200 [thread overview]
Message-ID: <3786074.FTf50R74LC@xps13> (raw)
In-Reply-To: <1474614646-23648-1-git-send-email-yuanhan.liu@linux.intel.com>
2016-09-23 15:10, Yuanhan Liu:
> Commit c711ccb30987 ("ivshmem: remove library and its EAL integration")
> removed ivshmem support, but seems David forgot to remove the another
> piece of code: code for RTE_EAL_SINGLE_FILE_SEGMENTS, which is introduced
> when ivshmem was firstly added.
It is not a mistake. We thought it is used by container use case.
next prev parent reply other threads:[~2016-09-23 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 7:10 Yuanhan Liu
2016-09-23 8:50 ` Thomas Monjalon [this message]
2016-09-23 9:14 ` Yuanhan Liu
2016-09-23 10:08 ` Tan, Jianfeng
2016-09-30 14:32 ` David Marchand
2016-09-30 14:48 ` Sergio Gonzalez Monroy
2016-10-03 14:08 ` Thomas Monjalon
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=3786074.FTf50R74LC@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=yuanhan.liu@linux.intel.com \
/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).