From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by dpdk.org (Postfix) with ESMTP id 9EB60CF9 for ; Sun, 9 Aug 2015 10:57:40 +0200 (CEST) Received: by wijp15 with SMTP id p15so102800373wij.0 for ; Sun, 09 Aug 2015 01:57:40 -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=EDAZiHq8CYId6E4Vz2q8Uz/K1/bDauafxVLBhK55n14=; b=ZVVzMTk3rcTXTRejMWbxHlqDW2W/OGeChTjDM7bPSXEg7DbdRpKRmsT4S7xlaujK41 HYH3wvJi38Rm/SsiweEWag2yS4AyrV5r+Th91ksRTo5Zzeg+RXS2/ggflOPu5UDd8n5y aCSaQiLFrKrcna7QORNNNucfuU0FTOs62R8ax8JZmuCtUb8EXkQkCNxm5+he7J+FVA8J VrZ6YwlVUACyCdwrdMX2cCcgsJ9j2+Rq9xJTyw+2MoVXenJIYQr2OBhgNDLykTxt7lMG 40sCsLIkyxZPZ2xwg+sJi0XSJxV+zYbZMo8SnQ1HiIr8t+7UbkFWrC142Yvt3+OK6LFe 8GMw== X-Gm-Message-State: ALoCoQmnICKzqvPSTwlc6o5L3ZuVki1rmaDkbI+Bw4QIp+Yfi6w6txnyHZFu3h0v6bfs6xHV287D X-Received: by 10.194.20.161 with SMTP id o1mr35211888wje.32.1439110660419; Sun, 09 Aug 2015 01:57:40 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by smtp.gmail.com with ESMTPSA id di7sm7679928wib.23.2015.08.09.01.57.39 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 09 Aug 2015 01:57:39 -0700 (PDT) From: Thomas Monjalon To: Jan Kiszka Date: Sun, 09 Aug 2015 10:56:26 +0200 Message-ID: <1801553.GZ2Pizxj8G@xps13> Organization: 6WIND User-Agent: KMail/4.14.8 (Linux/4.0.4-2-ARCH; KDE/4.14.8; x86_64; ; ) In-Reply-To: <55C5AD1F.9020902@siemens.com> References: <55C4EB5C.4080001@siemens.com> <55C5AD1F.9020902@siemens.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] vhost-switch example: huge memory need and CRC off-loading issue 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: Sun, 09 Aug 2015 08:57:40 -0000 2015-08-08 09:17, Jan Kiszka: > On 2015-08-08 02:39, Ouyang, Changchun wrote: > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jan Kiszka > >> - MAX_QUEUES of 512 causes pretty high memory need for the application > >> (something between 1 and 2G) - is that really needed? I'm now running > >> with 32, and I'm able to get away with 256M. Can we tune this > >> default? > > > > Don't think we need change default just because your platform is 32, > > Well, my platform is 128, other platform may have other value, :-) > > Then let's make it configurable or explore the actual device needs > before allocating the buffer. The impact on memory consumption is way > too big to hard-code this, specifically as this is per physical port IIUC. You can add a run-time option and/or add a comment in the documentation. It is just an example, so it must be simple to understand.