From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 89142A0545; Tue, 20 Dec 2022 11:33:23 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2DAAA40685; Tue, 20 Dec 2022 11:33:23 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 4B77540395 for ; Tue, 20 Dec 2022 11:33:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1671532401; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=bAQlWzHSRv548KCstYxyZS0HTWdh/mh34aMrf3d+SS8=; b=iOClm/KPCQn7DfWLIeIgbUinFICwpQavRnEt9eJb2oj1ONZG+TucM4Ywe2DEGvePQOxgQR JYsQpmd2+/iA8o2z7HOX4vbGWgWtA64Iwl6ttT1JxB3RNXKYaF8gHkSqQotboGBW+vLRNe blUqgf6iscTMbhBVXzz+7qAgxCk7K98= Received: from mail-pf1-f200.google.com (mail-pf1-f200.google.com [209.85.210.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-441-E0rM_kJpNNWbKLSm_LQcEg-1; Tue, 20 Dec 2022 05:33:20 -0500 X-MC-Unique: E0rM_kJpNNWbKLSm_LQcEg-1 Received: by mail-pf1-f200.google.com with SMTP id v16-20020a62a510000000b005745a58c197so6635119pfm.23 for ; Tue, 20 Dec 2022 02:33:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=bAQlWzHSRv548KCstYxyZS0HTWdh/mh34aMrf3d+SS8=; b=ccNvurMSRQfPT5xPzPMltHoqgtpcPemAGMtEQa75dvdPLQiHowr0hk62U52lJDAM+x 9+DhUVdmAkBGHbwuNRHSWbw0vlIWfgzgGwLHI7Q4UnIgEdcaDRgRSlXhDrnpQz493NV+ x0SBpDRdd6dBORi/1U35bdjFTV4zxiHpvYy7s0utn/Q9ylw9GU4BqLWcT4q1TImqwZrM 5N3ej08KegVL1WPtf7WsTLwvBf97nT8fTohuT2QFSw6/uegT3+8l6lUJ6Gqe1hneq7os 2Mapoa2kPiErOwLXF3VNt+Ji5OtCfnQaFO7oNDcZ0SY8z3ODMfzRCHprgDaqnAWzTTuT Lgdw== X-Gm-Message-State: ANoB5pnyPC1Qrew0gEFuUyYEV6Zwscid0HnTZTtEZeHJekIIhajZZdIa CFHoJSc4DLxGhsgji4Rwi7iDKUji+1fty6tctkCCpF3LHB4bqt1NxdY1lZm2sNxiinbCDdiv5NZ T4DPDJXTtw/kzbLJlLwo= X-Received: by 2002:a17:902:7688:b0:186:971b:b7e5 with SMTP id m8-20020a170902768800b00186971bb7e5mr97226837pll.54.1671532399503; Tue, 20 Dec 2022 02:33:19 -0800 (PST) X-Google-Smtp-Source: AA0mqf6WGwx4VPFsRtnpNOV9hM+v6fNNKR1s9hg94E9PrKCWERGPIEocAWY4qZDR9mBIZrcL0k/po9yQz8H31K8DiSE= X-Received: by 2002:a17:902:7688:b0:186:971b:b7e5 with SMTP id m8-20020a170902768800b00186971bb7e5mr97226826pll.54.1671532399221; Tue, 20 Dec 2022 02:33:19 -0800 (PST) MIME-Version: 1.0 References: <20221117065726.277672-1-kaisenx.you@intel.com> <3ad04278-59c0-0c60-5c8c-9e57f33bb0de@amd.com> In-Reply-To: From: David Marchand Date: Tue, 20 Dec 2022 11:33:07 +0100 Message-ID: Subject: Re: [PATCH] net/iavf:fix slow memory allocation To: "You, KaisenX" Cc: Ferruh Yigit , "dev@dpdk.org" , "Burakov, Anatoly" , "stable@dpdk.org" , "Yang, Qiming" , "Zhou, YidingX" , "Wu, Jingjing" , "Xing, Beilei" , "Zhang, Qi Z" , Luca Boccassi , "Mcnamara, John" , Kevin Traynor X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Tue, Dec 20, 2022 at 11:12 AM You, KaisenX wrote: > > I tried to play a bit with a E810 nic on a dual numa and I can't see anything > > wrong for now. > > Can you provide a simple and small reproducer of your issue? > > > > Thanks. > > > This is my environment: > Enter "lscpu" on the command line: > NUMA: > NUMA node(s): 2 > NUMA node0 CPU(S) : 0-27,56-83 > NUMA node1 CPU(S) : 28-55,84-111 > > List the steps to reproduce the issue: > > 1. create vf and blind to dpdk > echo 1 > /sys/bus/pci/devices/0000\:ca\:00.0/sriov_ numvfs > ./usertools/dpdk-devbind. py -b vfio-pci 0000:ca:01.0 > 2. launch testpmd > ./x86_ 64-native-linuxapp-clang/app/dpdk-testpmd -l 28-48 -n 4 -a 0000:ca:01.0 > --file-prefix=dpdk_ 525342_ 20221104042659 -- -i --rxq=256 --txq=256 > --total-num-mbufs=500000 > > Parameter Description: > "-l 28-48":The range of parameter values after "-l" must be on "NUMA node1 CPU(S)" > "0000:ca:01.0":inset on node1 - Using 256 queues is not supported upstream... iavf_dev_configure(): large VF is not supported I would really love that Intel stops building/testing features with this out of tree driver........ We have lost and still lose so much time because of it. - Back to your topic. Can you try this simple hack: diff --git a/lib/eal/common/eal_common_thread.c b/lib/eal/common/eal_common_thread.c index c5d8b4327d..92160c7fa6 100644 --- a/lib/eal/common/eal_common_thread.c +++ b/lib/eal/common/eal_common_thread.c @@ -253,6 +253,7 @@ static void *ctrl_thread_init(void *arg) void *routine_arg = params->arg; __rte_thread_init(rte_lcore_id(), cpuset); + RTE_PER_LCORE(_socket_id) = SOCKET_ID_ANY; params->ret = pthread_setaffinity_np(pthread_self(), sizeof(*cpuset), cpuset); if (params->ret != 0) { -- David Marchand