DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: Tetsuya Mukawa <mtetsuyah@gmail.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/null: do not touch mbuf next or nb segs on Rx
Date: Fri, 12 May 2017 12:59:54 +0100	[thread overview]
Message-ID: <4c867262-a949-c4bd-3df7-a3ff3e48fd73@intel.com> (raw)
In-Reply-To: <20170509092437.652bac1c@platinum>

On 5/9/2017 8:24 AM, Olivier Matz wrote:
> On Thu,  4 May 2017 16:43:58 +0100, Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>> mbuf next and nb_segs fields already have the default values when get
>> from mempool, no need to update them in PMD.
>>
>> See: 8f094a9ac5d7 ("mbuf: set mbuf fields while in pool")
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>

> Reviewed-by: Olivier Matz <olivier.matz@6wind.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2017-05-12 11:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04 15:43 Ferruh Yigit
2017-05-09  7:24 ` Olivier Matz
2017-05-12 11:59   ` Ferruh Yigit [this message]

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=4c867262-a949-c4bd-3df7-a3ff3e48fd73@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=mtetsuyah@gmail.com \
    --cc=olivier.matz@6wind.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).