From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) by dpdk.org (Postfix) with ESMTP id 140E4593A for ; Thu, 22 May 2014 14:46:02 +0200 (CEST) Received: by mail-wg0-f42.google.com with SMTP id y10so3280375wgg.13 for ; Thu, 22 May 2014 05:46:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=Dtirup1gRn2Uh5pxPWe36Nvpz2ZYb/jDGsxvFVFW3Q0=; b=KwT2K9l907P1J/6QUVv3Hi+cCpgk4g45VsJnB4JkIPU7mk/TGKH0R22++upmO9oK9T 5CLoOieYijovBIa0VSsjL+ygwDZbmeQJSMVr2JXkHNXt+kOOo0wwMWeU9Ni6ZYezzif2 J6vEQtiTARrU7Wx4ZHSK2JFGlHKYQ3kA6wASdxI+9wQRRmdAg0F/aG2uNHD6Ll9hV/yH m21dJITr5dkllf8e0Kx/qq57Epz4nPs03yhwTo8Iuqv6ylAInom7V3smq+RXUdLA7866 ywVsTsJk0HvNqmeNy5A9lMwO8RlHj1tIassXBWMhNeVq0//KEOErLqgZi0HFcf/Gt/2v RfQg== X-Gm-Message-State: ALoCoQn4+VwaWkSOfUstLcwAShgFyenrIm5Y4gs7IpgzA9COvT388aZVkCt8xb4F8HaP89Jai1To X-Received: by 10.194.158.132 with SMTP id wu4mr1590495wjb.96.1400762772713; Thu, 22 May 2014 05:46:12 -0700 (PDT) Received: from xps13.localnet (6wind.net2.nerim.net. [213.41.180.237]) by mx.google.com with ESMTPSA id vp5sm26628974wjc.31.2014.05.22.05.46.10 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 May 2014 05:46:11 -0700 (PDT) From: Thomas Monjalon To: "Burakov, Anatoly" Date: Thu, 22 May 2014 14:46:08 +0200 Message-ID: <7296546.Pqjxyb6pDa@xps13> Organization: 6WIND User-Agent: KMail/4.13 (Linux/3.14.4-1-ARCH; KDE/4.13.0; x86_64; ; ) In-Reply-To: References: <1871082.JnAAVjVYKa@xps13> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v2 08/16] Add support for mapping devices through VFIO. X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2014 12:46:03 -0000 2014-05-22 12:37, Burakov, Anatoly: > > Yes, in some environments, it could be easier to be able to configure > > devices directly on application command line instead of having to call a > > python script. I think having a clear and extendable syntax to configure > > devices in command line could greatly improve usability. But it can be > > another step. > > That's probably out of scope for this patch. We can discuss this later > without stalling VFIO :) Yes, I agree to discuss it later. > > What do you think of _mp_sync or _mp_conf? > > Usage of the socket is to synchronize VFIO config between processes, > > right? > > More or less, yes. However, the code inside that file is the communication > mechanism. I.e. it's not actually synchronizing or configuring anything, > it's simply providing means to do so for primary and secondary processes, > so I don't think _mp_sync or _mp_conf is a good name for that. IMO > something like _mp_socket or similar (_mp_comm?) would be more appropriate. Yes I agree. But I stopped on the name for another thing: it's not really specific to vfio. Actually, vfio uses it for synchronization. But wouldn't it be more generic? -- Thomas