From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bradley.kite@gmail.com>
Received: from mail-lf0-f42.google.com (mail-lf0-f42.google.com
 [209.85.215.42]) by dpdk.org (Postfix) with ESMTP id 6DD456CA2
 for <users@dpdk.org>; Mon, 16 May 2016 18:32:10 +0200 (CEST)
Received: by mail-lf0-f42.google.com with SMTP id y84so119369181lfc.0
 for <users@dpdk.org>; Mon, 16 May 2016 09:32:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to;
 bh=V6ejMKVkuCOTJ+PQ48drtrK0LDlMkkc5sv2+RthQPFU=;
 b=KBMIinvoQ9tX105ur9MzokSq3+6cKW1hIxnhdZgOI9cRZumxFdDBVfRI6pwM7uU3Lx
 iyiB1dvbdXv94KAnEjE4HeVdoBqVPb1Kd7INRjzldysf3EsR2t8BZVEzxy3Dt8ifWNj3
 nJEyf3/ToP1E819JllmcjsLE4Aw8pVm6oNISitwWFnN+N+FxUFudekv0rlU9F+F5C2RT
 dA0+SJWQQNJw+FnwofuR/KCLgE/n7sQfxCkFG40D04zg9+9in+455Emv11YMx/zx7uQ+
 kNrrxwPKx7VNbI2lQazubwB84zK/4FlSCO53gYwyhm3keFEMpZAC8fshrVIoii7nmcaf
 DMTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:date:message-id:subject:from:to;
 bh=V6ejMKVkuCOTJ+PQ48drtrK0LDlMkkc5sv2+RthQPFU=;
 b=Q5Ft/whT3GDm5p1PtjgWuwHctLgdFVuhWaRgUVf5+w4m392FwgcnP9l03gNb38bZuV
 3ZZVyDTVX2I7qaal85C0pW8A+SstYA6Sa0hTojzHxPDlJw+S+2SKrH4zaYeRXKGM6zlB
 n1dkYL03fwsyD5vb+CZd2DL+4dtnwG/2C4+W+uEaFd+cdJB9hjR6Fm9+ycYtxG30/lvT
 zT/FzVNz4o2Jy+wQrIqjAeeLJSI4bwjW4NZq6Op2jDKi+fKj6T+KcQEFjolOvs+bjYAa
 MNw7URLqXBSyi+WVknMcUVEcq8TfpUdgMew0bFqjOU6TA1mtDtVeoIpdmL+DzTbXPlj6
 E0qg==
X-Gm-Message-State: AOPr4FVBJfDDleY0LaxA2Pa+216QNa9nZXbkiZZg0mIskrGh6WouWa/I4NRGdCbpbemLHZJwRA8oSrPdJSAJ/g==
MIME-Version: 1.0
X-Received: by 10.25.147.68 with SMTP id v65mr11986494lfd.9.1463416330128;
 Mon, 16 May 2016 09:32:10 -0700 (PDT)
Received: by 10.112.49.102 with HTTP; Mon, 16 May 2016 09:32:10 -0700 (PDT)
Date: Mon, 16 May 2016 17:32:10 +0100
Message-ID: <CA+JxU+5bwS5m2r+WxBFTTYXbhO_Q5y4it1zK4OpXgySvnzeOtQ@mail.gmail.com>
From: Bradley Kite <bradley.kite@gmail.com>
To: users@dpdk.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-users] Ability to clear/reset pipeline table?
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 16:32:10 -0000

Hi there,

The application I am writing needs to be able to clear all entries from a
table and then bulk-load a new set of entries - eg due to a "commit" action
by a user when applying new configuration, or perhaps by a CLI command (eg
to clear a NAT table).

I could not find a particularly easy way of doing this via the API's, so am
I correct in thinking that I need the application to also keep lists of all
keys within the table and then call rte_pipeline_table_entry_delete_bulk()
followed by rte_pipeline_table_entry_add_bulk()?

Does this approach not require twice as much memory if both the application
and the DPDK library keep copies of the keys for a table?

Any help or advice would be most appreciated.

Many thanks
--
Brad.