From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com
 [209.85.212.179]) by dpdk.org (Postfix) with ESMTP id 7F109B374
 for <dev@dpdk.org>; Sat, 30 Aug 2014 15:01:38 +0200 (CEST)
Received: by mail-wi0-f179.google.com with SMTP id q5so3817980wiv.12
 for <dev@dpdk.org>; Sat, 30 Aug 2014 06:05:56 -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=h+LwIUMxTIiLq/kFPIUlnJStvxcZS9zYW1WzAfTww78=;
 b=U5hdcIR9DYBU/AF5ENQBJhKti2dS0wEyq1B0MOHFYkFOINtQp084+opRmvbc6WvXTt
 7XcSf3nXTqR7NQ9IsolmXuTswp+ZHAS5qlQgBwqK9cljVsqt0DEvOkPUzdYF5Sxdui87
 J+fgVA/kyfDS6cae83OfpmM1mFIUKB1Ay2TybD0ZviUneeoibtMAs+XwirHGoL1XdxWd
 w52IIyiAfkun45xzTjbtAyCjZVB7qgril0UCZs517c2isZMs9DY1Xb10ZeMsu/+AZVw0
 f7io89CS/nsvjwB8Mkac+GZSu3fGh/Hs1YmMvUKlXsa/FBV++5nwcCgQhRiT/JflEzGI
 acqg==
X-Gm-Message-State: ALoCoQlgdCXy5EY9YFgbZNhz6jne+2xUIDJucmv1djrVYD8BP/cCH9KFxZv/QjeJi7ZF8sKOuX3y
X-Received: by 10.194.24.101 with SMTP id t5mr19936134wjf.76.1409403956680;
 Sat, 30 Aug 2014 06:05:56 -0700 (PDT)
Received: from xps13.localnet (APoitiers-651-1-187-227.w2-6.abo.wanadoo.fr.
 [2.6.186.227])
 by mx.google.com with ESMTPSA id k10sm7122070wjb.28.2014.08.30.06.05.52
 for <multiple recipients>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Sat, 30 Aug 2014 06:05:55 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Saygin, Artur" <artur.saygin@intel.com>
Date: Sat, 30 Aug 2014 15:03:54 +0200
Message-ID: <1971750.bXvAyT2929@xps13>
Organization: 6WIND
User-Agent: KMail/4.13.3 (Linux/3.15.8-1-ARCH; KDE/4.13.3; x86_64; ; )
In-Reply-To: <B1E02754DD4D4F4EAC7A14C1202CE62073E8E330@ORSMSX102.amr.corp.intel.com>
References: <B1E02754DD4D4F4EAC7A14C1202CE62073E8E330@ORSMSX102.amr.corp.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK and custom memory
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: Sat, 30 Aug 2014 13:01:38 -0000

Hello,

2014-08-29 18:40, Saygin, Artur:
> Imagine a PMD for an FPGA-based NIC that is limited to accessing certain
> memory regions <system, PCI, etc>.

Does it mean Intel is making an FPGA-based NIC?

> Is there a way to make DPDK use that exact memory?

Maybe I don't understand the question well, because it doesn't seem really
different of what other PMDs do.
Assuming your NIC is PCI, you can access it via uio (igb_uio) or VFIO.

> Perhaps this is more of a hugetlbfs question than DPDK but I thought I'd
> start here.

It's a pleasure to receive new drivers.
Welcome here :)

-- 
Thomas