From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Jianfeng Tan <jianfeng.tan@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Shijith Thotton <shijith.thotton@caviumnetworks.com>,
Gregory Etelson <gregory@weka.io>,
Harish Patil <harish.patil@cavium.com>,
George Prekas <george.prekas@epfl.ch>,
Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>,
Rasesh Mody <rasesh.mody@cavium.com>,
Lee Roberts <lee.roberts@hpe.com>
Subject: Re: [dpdk-dev] [PATCH] igb_uio: prevent reset for a list of devices
Date: Sat, 04 Nov 2017 00:03:32 +0100 [thread overview]
Message-ID: <2051591.HpGYabZJN9@xps> (raw)
In-Reply-To: <20171103223822.28852-1-ferruh.yigit@intel.com>
03/11/2017 23:38, Ferruh Yigit:
> Some devices are having problem on device reset that happens during DPDK
> application exit [1].
>
> Create a static list of devices and exclude them from device reset.
[...]
> This is alternative approach to
> http://dpdk.org/dev/patchwork/patch/31144/
It is better to change the behaviour only for the misbehaving device,
as it is done with this alternative.
However as far as I understand, the change is removing a long delay due
to the reset, but re-enable a security hole due to the lack of reset.
So I think we must have a compilation option anyway, in order to let
the packager (or distribution) make this difficult decision.
The compilation option could be something like
RTE_BNX2X_PREFER_SECURITY_HOLE_THAN_LONG_RESTART
Feel free to find a better name :)
next prev parent reply other threads:[~2017-11-03 23:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 22:38 Ferruh Yigit
2017-11-03 23:03 ` Thomas Monjalon [this message]
2017-11-04 0:56 ` Mody, Rasesh
2017-11-06 18:48 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2017-11-06 23:55 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2017-11-07 11:50 ` Chas Williams
2017-11-07 13:02 ` Thomas Monjalon
2017-11-07 18:12 ` Chas Williams
2017-11-07 18:49 ` Ferruh Yigit
2017-11-07 20:47 ` Chas Williams
2017-11-07 22:26 ` Ferruh Yigit
2017-11-08 12:00 ` Chas Williams
2017-11-10 1:40 ` Ferruh Yigit
2017-11-13 23:46 ` Stephen Hemminger
2017-11-07 13:13 ` Stephen Hemminger
2017-11-07 18:14 ` Chas Williams
2017-11-09 17:20 ` [dpdk-dev] ugb_uio: r3.8xlarge bind failure Gregory Etelson
2017-11-10 1:42 ` Ferruh Yigit
2017-11-10 2:11 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2017-11-10 6:36 ` [dpdk-dev] " Gregory Etelson
2017-11-15 15:44 ` Ferruh Yigit
2017-11-15 16:30 ` Gregory Etelson
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=2051591.HpGYabZJN9@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=george.prekas@epfl.ch \
--cc=gregory@weka.io \
--cc=harish.patil@cavium.com \
--cc=jianfeng.tan@intel.com \
--cc=jingjing.wu@intel.com \
--cc=lee.roberts@hpe.com \
--cc=rasesh.mody@cavium.com \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=shijith.thotton@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).