From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <vincent.jardin@6wind.com>
Received: from mail-wg0-f48.google.com (mail-wg0-f48.google.com [74.125.82.48])
 by dpdk.org (Postfix) with ESMTP id 7B92258EF
 for <dev@dpdk.org>; Fri, 19 Jul 2013 18:34:44 +0200 (CEST)
Received: by mail-wg0-f48.google.com with SMTP id f11so4107196wgh.3
 for <dev@dpdk.org>; Fri, 19 Jul 2013 09:35:05 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=google.com; s=20120113;
 h=message-id:date:from:organization:user-agent:mime-version:to
 :subject:references:in-reply-to:content-type
 :content-transfer-encoding:x-gm-message-state;
 bh=nMXdpGPBLIvuDEfKa5K72f9nqL4Q4dncY7g6WEwxQGE=;
 b=Wg7yeAAKB7i1iOmRcojD4UjlOtvFKniSv07GJr4goL7h+vo8WuyPkxkSZsVDd/E3+o
 GxrrtdWhxT3Tg5PsedkB1peCeS+F1lgrIKH+6AFG7ZDAMXqjgq0V8ClA/LYgLWVUQskm
 JhNnHMn6GUazjrbOdC7SpjL/lcntCGMXPSKr3dmFDGcfZtbKUymzfAcD2cLyiQnf9lnl
 N5UHI8tlRG2gdySOuL1eA5z6ZNQS0YJ4yRPOSwywbHf3HYTzll9thtP/aKl0HURACKGo
 +6fSGhJ42v1LZcpfe3PeSe+gLi9q293E83p2qwduA7QlPOMB6PqBGdD/NnA6SVdt/L+w
 jUTA==
X-Received: by 10.180.185.74 with SMTP id fa10mr12075464wic.26.1374251705097; 
 Fri, 19 Jul 2013 09:35:05 -0700 (PDT)
Received: from saturne.dev.6wind.com ([2a01:e35:8a8e:1b70:226:b9ff:fec7:e133])
 by mx.google.com with ESMTPSA id
 j20sm24113920wie.7.2013.07.19.09.35.02 for <dev@dpdk.org>
 (version=TLSv1 cipher=RC4-SHA bits=128/128);
 Fri, 19 Jul 2013 09:35:04 -0700 (PDT)
Message-ID: <51E96AB5.3060509@6wind.com>
Date: Fri, 19 Jul 2013 18:35:01 +0200
From: Vincent JARDIN <vincent.jardin@6wind.com>
Organization: www.6wind.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: dev@dpdk.org
References: <51E80CF9.6030005@gmail.com> <51E94D83.5040603@iki.fi>
In-Reply-To: <51E94D83.5040603@iki.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQlxMFlNtzHb5DwoTlsyl61sSr3jYj1omgxlrleF8cwHLobY2TIRPp4MN9hHY/qoVvpctPgh
Subject: Re: [dpdk-dev] Any ideas how to stop DPDK from banning me from the
 box.
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 16:34:44 -0000

On 19/07/2013 16:30, Antti Kantee wrote:
> Semi-related: why does DPDK take a blacklist instead of a list of
> devices that it should use (perhaps with a special value "all" in case
> someone really wants that behavior)?  Historical reasons?
>
> (yes, I've also bricked my ssh connections several times)

Antti, you are right. Should you need to make it better with a device 
name, your patch can be included.

About such ssh connection, we did not feel the pain at 6WIND since we 
have a stack that manages such issues so it does not break, but your 
request is valid.

Looking for any patch that would help,
   Vincent