Soft Patch Panel
 help / color / mirror / Atom feed
From: Yasufumi Ogawa <usufumu@gmail.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: ogawa.yasufumi@lab.ntt.co.jp, spp@dpdk.org
Subject: Re: [spp] [PATCH 0/2] Revise setup manual
Date: Fri, 25 May 2018 13:34:06 -0700	[thread overview]
Message-ID: <924a0dfb-5a57-9500-1562-60d52c5957e0@gmail.com> (raw)
In-Reply-To: <964f2aad-1510-26be-d3ec-7fcbbd1b8cd5@intel.com>

On 2018/05/24 6:05, Ferruh Yigit wrote:
> On 5/15/2018 2:21 AM, ogawa.yasufumi@lab.ntt.co.jp wrote:
>> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
>>
>> Hi,
>>
>> SPP is a kind of DPDK multi-process application and ASLR should be
>> disabled to running SPP stably.  To use pcap PMD, DPDK should be
>> configured with CONFIG_RTE_LIBRTE_PMD_PCAP=y and compiled before SPP
>> compilation. This patch is for adding instruction for ASLR and pcap.
>>
>> This patch also includes misc update for revising descriptions or
>> command examples.
>>
>> Thanks,
>> Yasufumi
>>
>>
>> Yasufumi Ogawa (2):
>>    docs: add instruction for disabling ASLR
>>    docs: revise getting started guide
> Hi Yasufumi,
>
> I can't apply these patches on top of latest master, can you please check, or
> did I missed some patches in the middle?
Sorry! It might be my fault. I'd check and correct it.

Thanks,
Yasufumi

  reply	other threads:[~2018-05-25 20:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15  1:21 ogawa.yasufumi
2018-05-15  1:21 ` [spp] [PATCH 1/2] docs: add instruction for disabling ASLR ogawa.yasufumi
2018-05-15  1:21 ` [spp] [PATCH 2/2] docs: revise getting started guide ogawa.yasufumi
2018-05-24 13:05 ` [spp] [PATCH 0/2] Revise setup manual Ferruh Yigit
2018-05-25 20:34   ` Yasufumi Ogawa [this message]
2018-05-28  9:47     ` Yasufumi Ogawa
2018-05-28 12:26       ` Ferruh Yigit
2018-05-28 12:27 ` Ferruh Yigit

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=924a0dfb-5a57-9500-1562-60d52c5957e0@gmail.com \
    --to=usufumu@gmail.com \
    --cc=ferruh.yigit@intel.com \
    --cc=ogawa.yasufumi@lab.ntt.co.jp \
    --cc=spp@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).