From: Eric Zhang <eric.zhang@windriver.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
<santosh.shukla@caviumnetworks.com>
Cc: <dev@dpdk.org>, <Allain.Legacy@windriver.com>,
<Matt.Peters@windriver.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] eal: add eal option to configure iova mode
Date: Mon, 1 Oct 2018 12:00:13 -0400 [thread overview]
Message-ID: <8d78b625-8366-d033-86ca-7264b0405b77@windriver.com> (raw)
In-Reply-To: <e1d2312e-08cd-c21d-126a-febfc351fde3@intel.com>
On 09/26/2018 08:42 AM, Burakov, Anatoly wrote:
> On 18-Sep-18 8:10 PM, eric zhang wrote:
>> From: Santosh Shukla <santosh.shukla@caviumnetworks.com>
>>
>> In the case of user don't want to use bus iova scheme and want
>> to override.
>>
>> For that, Adding eal option --iova-mode=<string> where valid input
>> string is 'pa' or 'va'.
>>
>> Signed-off-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
>> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
>> ---
>
> Needs documentation update in Programmer's Guide to explain why such a
> thing might be needed, and update EAL parameter guides.
>
> For the patch itself,
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
Thanks Anatoly. Documentations were updated and patch is at
http://patchwork.dpdk.org/patch/45785/. Would you please give a review?
Eric
next prev parent reply other threads:[~2018-10-01 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 19:10 eric zhang
2018-09-18 19:10 ` [dpdk-dev] [PATCH v2 2/2] eal: force IOVA to particular mode eric zhang
2018-09-24 20:42 ` Zhang, Qing Long (Eric)
2018-09-25 7:16 ` Santosh Shukla
2018-09-25 20:11 ` Zhang, Qing Long (Eric)
2018-09-26 7:11 ` Hemant
2018-09-26 12:43 ` Burakov, Anatoly
2018-09-26 7:10 ` [dpdk-dev] [PATCH v2 1/2] eal: add eal option to configure iova mode Hemant
2018-09-26 12:42 ` Burakov, Anatoly
2018-10-01 16:00 ` Eric Zhang [this message]
2018-10-02 8:30 ` Ferruh Yigit
-- strict thread matches above, loose matches on Subject: below --
2018-09-18 19:09 eric zhang
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=8d78b625-8366-d033-86ca-7264b0405b77@windriver.com \
--to=eric.zhang@windriver.com \
--cc=Allain.Legacy@windriver.com \
--cc=Matt.Peters@windriver.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=santosh.shukla@caviumnetworks.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).