patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Chen, Jing D" <jing.d.chen@intel.com>,
	"Wang, Xiao W" <xiao.w.wang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/fm10k: fix secondary process crash
Date: Mon, 3 Apr 2017 10:51:37 +0100	[thread overview]
Message-ID: <508d41e3-3f4e-99ef-3e46-921e2c4d683a@intel.com> (raw)
In-Reply-To: <4341B239C0EFF9468EE453F9E9F4604D3C62159A@shsmsx102.ccr.corp.intel.com>

On 4/1/2017 4:22 AM, Chen, Jing D wrote:
> 
> 
>> -----Original Message-----
>> From: Wang, Xiao W
>> Sent: Tuesday, March 28, 2017 11:59 AM
>> To: Chen, Jing D <jing.d.chen@intel.com>
>> Cc: dev@dpdk.org; Wang, Xiao W <xiao.w.wang@intel.com>;
>> stable@dpdk.org
>> Subject: [PATCH] net/fm10k: fix secondary process crash
>>
>> If the primary process has initialized all the queues to vector pmd mode, the
>> secondary process should not use scalar code path, because the per queue
>> data structures haven't been prepared for that, e.g. txq->ops is for vector Tx
>> rather than scalar Tx.
>>
>> Fixes: a6ce64a97520 ("fm10k: introduce vector driver")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
> Acked-by : Jing Chen <jing.d.chen@intel.com>

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

  reply	other threads:[~2017-04-03  9:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28  3:58 Xiao Wang
2017-03-31  1:30 ` Chen, Jing D
2017-04-01  0:20   ` Wang, Xiao W
2017-04-01  3:22 ` Chen, Jing D
2017-04-03  9:51   ` Ferruh Yigit [this message]
2017-05-22 15:22 Xiao Wang

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=508d41e3-3f4e-99ef-3e46-921e2c4d683a@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jing.d.chen@intel.com \
    --cc=stable@dpdk.org \
    --cc=xiao.w.wang@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).