From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 169831AEEB for ; Mon, 18 Sep 2017 16:51:44 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Sep 2017 07:51:35 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,413,1500966000"; d="scan'208";a="1173319544" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.57]) ([10.237.220.57]) by orsmga001.jf.intel.com with ESMTP; 18 Sep 2017 07:51:33 -0700 To: Shreyansh Jain , dev@dpdk.org Cc: hemant.agrawal@nxp.com References: <20170823141213.25476-1-shreyansh.jain@nxp.com> <20170909112132.13936-1-shreyansh.jain@nxp.com> <20170909112132.13936-8-shreyansh.jain@nxp.com> From: Ferruh Yigit Message-ID: <144b891a-5457-5a3e-5c0d-33ef02cccc07@intel.com> Date: Mon, 18 Sep 2017 15:51:32 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20170909112132.13936-8-shreyansh.jain@nxp.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH v4 07/41] bus/dpaa: enable DPAA IOCTL portal driver X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2017 14:51:46 -0000 On 9/9/2017 12:20 PM, Shreyansh Jain wrote: > Userspace applications interact with DPAA blocks using this IOCTL driver. > > Signed-off-by: Geoff Thorpe > Signed-off-by: Hemant Agrawal > Signed-off-by: Shreyansh Jain <...> > +static int fd = -1; > +static pthread_mutex_t fd_init_lock = PTHREAD_MUTEX_INITIALIZER; > + > +static int check_fd(void) > +{ > + int ret; > + > + if (fd >= 0) > + return 0; > + ret = pthread_mutex_lock(&fd_init_lock); Do you need to link against pthred library for this": LDLIBS += -lpthread <...> > +/* The process device underlies process-wide user/kernel interactions, such as > + * mapping dma_mem memory and providing accompanying ioctl()s. (This isn't used > + * for portals, which use one UIO device each.). > + */ > +#define PROCESS_PATH "/dev/fsl-usdpaa" Who is creating this file, who is responsible to responding ioctl() calls, there must a kernel module, right? <...>