From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.cs.Stanford.EDU (smtp2.cs.stanford.edu [171.64.64.26]) by dpdk.org (Postfix) with ESMTP id C71105581 for ; Tue, 20 Sep 2016 02:12:10 +0200 (CEST) Received: from mail-it0-f43.google.com ([209.85.214.43]:33167) by smtp2.cs.Stanford.EDU with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84_2) (envelope-from ) id 1bm8fR-0001wc-Bb for users@dpdk.org; Mon, 19 Sep 2016 17:12:10 -0700 Received: by mail-it0-f43.google.com with SMTP id x192so22996732itb.0 for ; Mon, 19 Sep 2016 17:12:09 -0700 (PDT) X-Gm-Message-State: AE9vXwOEfkPMTnMsmPaFXLtqKeb/6L+zeQ5mNWKIT+7b9PJSYQEnM+4c/muTURYLvzBhojZ/UQzXFrKhdMqLmw== X-Received: by 10.36.65.155 with SMTP id b27mr956767itd.56.1474330328956; Mon, 19 Sep 2016 17:12:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.105.5 with HTTP; Mon, 19 Sep 2016 17:11:28 -0700 (PDT) From: John Ousterhout Date: Mon, 19 Sep 2016 17:11:28 -0700 X-Gmail-Original-Message-ID: Message-ID: To: users@dpdk.org X-Spam-Score: -1.0 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin on smtp2.cs.Stanford.EDU X-Scan-Signature: 3e263c829a24e9e508d860775f9d44fb Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] False conflicts over .rte_config lock file X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 00:12:11 -0000 I recently upgraded to the DPDK git head, and am now getting messages of the following form when I run RAMCloud using DPDK: EAL: Error - exiting with code: 1 Cause: Cannot create lock on '/home/ouster/.rte_config'. Is another primary process running? This is a false conflict that is coming about because several different DPDK applications are starting up on several different nodes (only one per node), but they are all running in the same shared NFS home directory. It appears that DPDK is choosing the same lock file for all of the nodes, which fools it into thinking that multiple DPDK applications are running on the same node. Is there a way to get rid of this conflict? I have seen the --file-prefix in the documentation, but generating a unique prefix for each application is nontrivial. I suppose I could just generate a large random number and assume there will be no conflicts, but I'm wondering if there is a cleaner mechanism supported by DPDK. I would guess that running multiple DPDK apps on different nodes in a shared directory might be fairly common? -John-