From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f50.google.com (mail-pg0-f50.google.com [74.125.83.50]) by dpdk.org (Postfix) with ESMTP id 406B1F94 for ; Mon, 17 Apr 2017 18:54:38 +0200 (CEST) Received: by mail-pg0-f50.google.com with SMTP id 72so66135278pge.2 for ; Mon, 17 Apr 2017 09:54:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=eYhVzL8f4+6VbD3ya2aVsZ4Mq39yJD8BK0KTrjF7JMU=; b=A69pJxv1EP5ZWvQE2KJxBpORfVLxTV1g7yB77lxlqstQo3utbS8QfPHpccKXa6sRpm OEhNpIB8BEE+NdM9gbIB4qJF4j563dCjy4Mz0+4IDMGu+x2RfNp/EpYM2pLHuFIAAQ4M 9abe8M6GkFrrR60MdutevJQlwbSQZeX4syZQZ3jjr5Lpir9WeIX/34UFy1zwcqFwQmR9 nYMzFV3CPMTLmBvoSAuf9cZ7axxXJvCS3STvjLX4T+WEGW9ffDv1S/4HAmkhghta1R4+ CgKqs4nTGgwtgqMFoN8XJ5wuKH72A9sjz8ivHK7zhxlQziJHRi2jpSgej/8sNrTu53Eg xQvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=eYhVzL8f4+6VbD3ya2aVsZ4Mq39yJD8BK0KTrjF7JMU=; b=pichizJxlqu3mvWrc2LI1/wJ/xUcVGC0/Es75LpzIjlvfhBPc+fIU1a4fwH7WnChOV R9mmJYsS40NVEzGPNBW6sFecd+NVVq2IyzrMv1VidSsQhN4k0UL+QubExVNSTzLvKINk /sMWRGqoiLBciVSSExpvQVCgR1UkA0A26Z364LGLttqzTT4f0QxhY+Bn4/5G2FYJLOKD CWGauRkFVdjJpTotxI9t7YdmwyCg8g9g8LN8P00gpkCOXZbkww9aI+zMQ3/ADNNlWRFh 52OazKFnVXg9sihbEdtYfJcRSqk7hLh5EIQkZ8tiL4gk1uls8SpVEVkpEN/HvBsS/xER xS3A== X-Gm-Message-State: AN3rC/795Y4IMLc+u4gxQnjAjprSMtaO95p+adxKIqq8oy8+3Yi/TgtI fcCmfLfjIuKr5g== X-Received: by 10.98.101.7 with SMTP id z7mr12912722pfb.81.1492448077424; Mon, 17 Apr 2017 09:54:37 -0700 (PDT) Received: from xeon-e3 (76-14-206-252.or.wavecable.com. [76.14.206.252]) by smtp.gmail.com with ESMTPSA id m3sm19300575pgn.30.2017.04.17.09.54.36 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 17 Apr 2017 09:54:37 -0700 (PDT) Date: Mon, 17 Apr 2017 09:54:30 -0700 From: Stephen Hemminger To: "Fu, Qiaobin" Cc: "users@dpdk.org" Message-ID: <20170417095430.52cd5fdf@xeon-e3> In-Reply-To: <070B2881-A8CF-4106-9921-41E4AEB288A4@bu.edu> References: <070B2881-A8CF-4106-9921-41E4AEB288A4@bu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-users] DPDK hash table dynamic growth X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2017 16:54:38 -0000 On Mon, 17 Apr 2017 15:47:59 +0000 "Fu, Qiaobin" wrote: > Hello, >=20 > Currently, I am using the hash library to handle network flows defined as= source and destination IP addresses. I need to find a way to alleviate mem= ory pressure when the table is full. However, after some research, I didn= =E2=80=99t find any hints on the dynamic growth in the hash library. Could = anyone point me some hints on this? Thanks. >=20 > Best, > Qiaobin If you need growing hash table, I recommend the lock-free hash table in the= Linux userspace RCU library; rather than the more limited DPDK one.