From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rahul.lakkireddy@chelsio.com>
Received: from stargate.chelsio.com (stargate.chelsio.com [12.32.117.8])
 by dpdk.org (Postfix) with ESMTP id 934C51B22D
 for <dev@dpdk.org>; Thu, 19 Oct 2017 16:47:54 +0200 (CEST)
Received: from localhost (scalar.blr.asicdesigners.com [10.193.185.94])
 by stargate.chelsio.com (8.13.8/8.13.8) with ESMTP id v9JElmZC019719;
 Thu, 19 Oct 2017 07:47:49 -0700
Date: Thu, 19 Oct 2017 20:16:43 +0530
From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: He JianJun <jason@featen.com>
Cc: dev@dpdk.org, kumaras@chelsio.com, nirranjan@chelsio.com,
 indranil@chelsio.com
Message-ID: <20171019144642.GA9777@chelsio.com>
References: <CAEZ0pjp5ZOg8KdBt=f8B2sVo=dqMfB1HwhVUAcSGjsNLiEhiaw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAEZ0pjp5ZOg8KdBt=f8B2sVo=dqMfB1HwhVUAcSGjsNLiEhiaw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Subject: Re: [dpdk-dev] Does cxgbe support multiple processes mode
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <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: Thu, 19 Oct 2017 14:47:55 -0000

On Tuesday, October 10/17/17, 2017 at 23:26:19 -0700, He JianJun wrote:
> Does cxgbe support multiple processes mode? If not, how can we implement it?
> 
> I tried with 17.08 code, secondary process will crash at sge.c line 1098.
> t4_eth_xmit()
> because txq->eth_dev->data is NULL.
> 
> I am guessing cxgbe driver does not support multiple processes mode,
> although I just need multiple tx in multiple processes.
> 
> Thansk.
> featen

Thanks for reporting this.  We're looking into this issue internally
and get back to you soon.

Thanks,
Rahul