From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f48.google.com (mail-it0-f48.google.com [209.85.214.48]) by dpdk.org (Postfix) with ESMTP id EE5483238 for ; Tue, 8 Nov 2016 13:02:33 +0100 (CET) Received: by mail-it0-f48.google.com with SMTP id q124so93054557itd.1 for ; Tue, 08 Nov 2016 04:02:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lightcyber-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1SUXvafxKSsgsbO8h82y00/OdHt/p7xCEKBor9xhTIA=; b=raQZmUaIurff+b1DScIYcWpcX152t4AAmzfe+UjNscap3oYxbfuYvhv0Bsk8nmFNvK 8iBvgm4A9+gfbtpHqdYLGOTFLvFyjvrlcDDH4SsHqhjyBpkX0e+OTyc+8uBPD8GKGZFi wBWnrXDsT9150VQm4t47m9pIuwNqf66NtreVnfeRhVWhxYlw+yTcjVFXU8n2MFGZVhLi 7SoQ0SF+J5ZJFG+jjj+btMfZ5eZN/jpa61MQD17mOnM3JGK4cuxD2HbD7c9Q1mjwh2ei h4lUNYewh+y5kbHwrXht6ed47XuH5NuUvF7mOkCl81aFz+tAPqq/Z5Bo3gPbAaDTEDPp euiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1SUXvafxKSsgsbO8h82y00/OdHt/p7xCEKBor9xhTIA=; b=cYrVHFkhTD4qJYLELwSPurLy7jXcwTIsM4IjI2C3r/aNlgr5Xzg2RfqRwuEADnwKt0 x3V8WBPnpMrshltVvLHdjGlfcilkL/FW0iZ/m1q6VMNo6nXMDrts8atWhhGRLXc++MXU HWpGyG2BiJjVaGrIqE6uyF1tsa6npEiy2zgHNO8QCLt/A9OODMYCuk4ruOkIGGFNDLHe 6K/q8Mg3Yf62Cpc10noLz9HeQlU7ycKBM3pyYKcNWUrimkd7kfp2nqcijkMFyqQdOmPm 5h55WtM0ygG5lRfs5/k6foKgzYS5VyqM8Qo8JrgqSL5v3JZD1j129KHNVC5tqrF3OCHj 25Dg== X-Gm-Message-State: ABUngve5p/i4QTu6RqpgZZJwkckM8c2/7kk6ZbxU+5rEIpeJIJuJVzIWRc5RekDA9jlGj1G/O9GBmUyQsBCKKQ== X-Received: by 10.107.11.81 with SMTP id v78mr12477442ioi.20.1478606553177; Tue, 08 Nov 2016 04:02:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.110.197 with HTTP; Tue, 8 Nov 2016 04:02:32 -0800 (PST) In-Reply-To: References: <60A9A962-53C9-4050-8D84-74AD13CCE09B@intel.com> From: Keren Hochman Date: Tue, 8 Nov 2016 14:02:32 +0200 Message-ID: To: "Wiles, Keith" Cc: "dev@dpdk.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] Running 2 process on the same machine 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: Tue, 08 Nov 2016 12:02:34 -0000 Also, I can't understand how to define socket-mem. I did not see anything related to hugepages in /etc/sysctl.conf. Can i mount hugepages to 2 different dirs instead and use --huge-dir ? Thank you. On Tue, Nov 8, 2016 at 11:44 AM, Keren Hochman wrote: > Thank you for your response, I still can not run the 2 process together. > if I add --no-pci to one process it can replace white and black lists > right? > > Thanks, keren > > On Tue, Nov 8, 2016 at 12:36 AM, Wiles, Keith > wrote: > >> >> > On Nov 7, 2016, at 7:28 AM, Keren Hochman >> wrote: >> > >> > Hi, >> > I need to run 2 process that uses dpdk on the same machine. One uses >> dpdk >> > drivers, and the other just read from a pcap file. If I disable >> hugepages >> > in the second process rte_mempool_create fails. What is the correct wa= y >> to >> > handle this? >> >> If you look at the two scripts in Pktgen pktgen-master.sh and >> pktgen-slave.sh these two scripts setup two instances of pktgen on the s= ame >> machine. Plus you can read the README.md file. >> >> http://dpdk.org/browse/apps/pktgen-dpdk/refs/ >> >> You have to make sure you have enough memory (huge pages) allocated for >> both instances to run. >> >> Then use =E2=80=94file-prefix XX to give each instance a different prefi= x for the >> huge page files in /dev/hugepages if that is the location of the files o= n >> your system. I would remove any files in that directory to free up the >> memory. >> >> Use the =E2=80=94socket-mem to allocate the correct amount of memory for= each >> instances this way DPDK does not consume all the pages for a given insta= nce. >> >> Make sure you blacklist the ports you do not want on the first instance >> using -b option and then blacklist the ports from the first instance whi= le >> allowing the other ports to be used on the second one. >> >> That should do it for most cases. >> >> > >> > Thanks, Keren >> >> Regards, >> Keith >> >> >