From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk0-f46.google.com (mail-vk0-f46.google.com [209.85.213.46]) by dpdk.org (Postfix) with ESMTP id 1137C11C5; Mon, 27 Mar 2017 22:21:59 +0200 (CEST) Received: by mail-vk0-f46.google.com with SMTP id r69so65770082vke.2; Mon, 27 Mar 2017 13:21:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=s/WTlxNuBwtF3x9ZQ0fS5bhjEWQnBrA75P6ec2MSFkY=; b=noeCVFR7XDbJc1SpLtMoOHchrmgKQ+3Zki/Z5qUX3GzS6U0imGU3uv+CvrWhQTU82L RkxQN/n6YhUd8HwGu3gJ+9TKYVivbBuuoeO7qpwmZeIOaw+DmYQFIIK11cbHInCdjjPB vX0xt+B2wXh67kEMmIXZTHbEqJ8XVwAlgqc7l7w/9kzIN9bv3It8N74M1L2Q884Iu0eb ajigpJvNRzYKPW9dsxayPVSYKO11q72F3JBdTKP5SXQ91KPK0sso/cyszkQ9PeJgW0s2 Ot+no1A9lwq2/9mTCqp0k6VlclKT9fwUkTgxFHgEMlLk/7V3dFAfanbUoIvFmjpzY5Sa Kw8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=s/WTlxNuBwtF3x9ZQ0fS5bhjEWQnBrA75P6ec2MSFkY=; b=idtBxDUUmkzlArhoGDtIzFeZrOdcyVKJGRkJ5b+Qzi/GOf7t1xa4kT4hNOmwiHfNq4 13Ci8Q1lQbbf6UGc+gGanzLsQY62HLknyQJogUpfsWAlymAjy1Cu1yGB3TxgpdGXHmUD H7SdFdRHNvuh5ofdQdSUL+tMASHvq3xzQqNzRdkPTJ/td3g+xR4STzX8WStpqqGENik+ cZ0p8JN6ydS7qG6KfAJ8A5yzphO2NliMf0Hi+V/bzmpq80l24xxUK93Emy2OpHsnhdgw VosgWgaCJIhKtIFJZCZKNTvI86KNQsVy+Tz7Mk8uaFSioT5Zd4A8l09M0NHS4l26BuE1 sbGg== X-Gm-Message-State: AFeK/H2pFcqTzgLQHktD6A5+xcPpkoGMZInbf0oNeYEYn/fbhITRhgcc1DshEoBsLgP1zM+F10re+4dmC/rbfg== X-Received: by 10.176.80.148 with SMTP id c20mr3284697uaa.0.1490646118971; Mon, 27 Mar 2017 13:21:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.159.34.135 with HTTP; Mon, 27 Mar 2017 13:21:58 -0700 (PDT) In-Reply-To: <2601191342CEEE43887BDE71AB9772583FADFE79@IRSMSX109.ger.corp.intel.com> References: <2601191342CEEE43887BDE71AB9772583FADFE79@IRSMSX109.ger.corp.intel.com> From: Victor Detoni Date: Mon, 27 Mar 2017 17:21:58 -0300 Message-ID: To: "Ananyev, Konstantin" Cc: "dev@dpdk.org" , users@dpdk.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] [dpdk-dev] Segm fault to the update acl context 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, 27 Mar 2017 20:22:00 -0000 Hi Konstantin, Thank you for your questions. Please find below a sample of my code: After the program has started, I send sighup signals to update the acl context, like this: if (signup == SIGHUP) use_acl_ctx_swap = 1; ... During the SIGHUP processes I create a new/swap acl ctx and data structures using the app_acl_init, add_rules and setup_acl functions ... main_loop() ... if (use_acl_ctx_swap) { if (acl_search.num_ipv4) { rte_acl_classify( acl_config.swap_acx_ipv4[socketid], //use swap acl ctx acl_search.data_ipv4, acl_search.res_ipv4, acl_search.num_ipv4, DEFAULT_MAX_CATEGORIES); send_packets(acl_search.m_ipv4, acl_search.res_ipv4, acl_search.num_ipv4); } else { if (acl_search.num_ipv4) { rte_acl_classify( acl_config.acx_ipv4[socketid], acl_search.data_ipv4, acl_search.res_ipv4, acl_search.num_ipv4, DEFAULT_MAX_CATEGORIES); send_packets(acl_search.m_ipv4, acl_search.res_ipv4, acl_search.num_ipv4); } } When I update the acl ctx, rarely the program doesn't crash, mainly when I just increase de rules. Is there a another way to add new/remove rules in the acl ctx instead of sighup or control variables? thanks Victor On Mon, Mar 27, 2017 at 6:23 AM, Ananyev, Konstantin < konstantin.ananyev@intel.com> wrote: > Hi Victor, > > > hello, > > > > I'm running l3fwd-acl example as a daemon and trying to update acl > context > > with as a "swap" acl context, but the program stops with a segment fault > > statement. Even using variables to direct which acl context the main loop > > has to use, the program breaks. > > > > I have noticed that even when I update only the swap acl context, the acl > > structures are updated and the segment fault also happens. > > > > please, someone knows why this segment fault? > > As I remembers, l3fwd-acl doesn't support updating ACL ctx on the fly. > Could you explain a bit more what are you trying to do, or even better > provide some code example to reproduce the issue? > > Konstantin > >