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 0AA9C41E11; Wed, 8 Mar 2023 03:04:00 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DF30240EF0; Wed, 8 Mar 2023 03:03:59 +0100 (CET) Received: from mail-pl1-f178.google.com (mail-pl1-f178.google.com [209.85.214.178]) by mails.dpdk.org (Postfix) with ESMTP id 05CA640ED6 for ; Wed, 8 Mar 2023 03:03:57 +0100 (CET) Received: by mail-pl1-f178.google.com with SMTP id v11so16286342plz.8 for ; Tue, 07 Mar 2023 18:03:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; t=1678241037; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=9ipRjNFBneQJVUtK22ZX5SjeiwteWpYslvOdyM+o2Lo=; b=wpQXv44ciGoqCFC2ihzugs2pokxOWHahFAsqrDZ3tVSsMuznAzIVQOSPgnLHyyB/y9 n2AOE6tIgyfcx800bEXJ9Dnf7B1IYv6LyIBMhr6ZwBXBKlFwuTYwH9JFQkho8AyES2RD o/1anErdUl/Eh4BtFRBgWC4gkyhQllCOGeiu1qjOQs9m4ftGelhadYL7St9Nan27xPhp 3swFbUvZDM/nWCxV2S294xvVrfEhxlof4mT4ps+Um3fnKBXIo3FwCliREFR5du54hzGw YKtqeTCTgn1gS4J2vCgA/ZbprkV0Gd44ye3oBfk28ekg9XgB+kstFrROtNefWHkvCWvW aoOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678241037; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=9ipRjNFBneQJVUtK22ZX5SjeiwteWpYslvOdyM+o2Lo=; b=KeHp/ql4++HonhqYnyPcP6v0ZzZ1RZCVl0HBFJ77re6AQlxmXXSLwxbkwYFrzLeAa7 V1emzhN4Xp3UWcL11M77S7vejf5zYSlcgOmZJYF7l6fbpFfx9L1cHfO1MmsicX4wLWVn gbVXYSvaomKYbtayUN6vIced06FC8Cam3stAC+wIU4+lBgRLo/CZWd4n+81U+B6mYD9u uu3BCHX3pk6TtTQ3HmnhwGxfpBfFvlmrHmUe2YqdGSGg5adSjdx8Rv8HDnOwSQG0OwFX WcEKtI9wCkc4AGlLsZ3Gwk/18miD+FgWZD2GGYD+JkujbCvt1/ssf5h0j6dgFLpLluV2 IBNg== X-Gm-Message-State: AO0yUKVy+MXzY2eZk8MrByHODS+Z58lrfIpKfaSEt7ZUDclbnPZ95ONH UlNZ+LUtoNqGAbHHzQW9u+2qnQ== X-Google-Smtp-Source: AK7set8u89AqBFOleAdrxHaJR4oNO3YA95BSQEyzl96V5aSR/VonFEebNzMNkMd1ZBElw8jtdIKHsQ== X-Received: by 2002:a05:6a20:e688:b0:cb:ac6c:139d with SMTP id mz8-20020a056a20e68800b000cbac6c139dmr16586847pzb.9.1678241036989; Tue, 07 Mar 2023 18:03:56 -0800 (PST) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id i23-20020aa79097000000b00589a7824703sm8508514pfa.194.2023.03.07.18.03.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 Mar 2023 18:03:56 -0800 (PST) Date: Tue, 7 Mar 2023 18:03:55 -0800 From: Stephen Hemminger To: fengchengwen Cc: , Bruce Richardson Subject: Re: [PATCH v3 2/2] eal: add option to put timestamp on console output Message-ID: <20230307180355.0a8443e9@hermes.local> In-Reply-To: <2f046d72-355a-93a5-ede6-0f729e9e525b@huawei.com> References: <20200814173441.23086-1-stephen@networkplumber.org> <20230306192810.106154-1-stephen@networkplumber.org> <20230306192810.106154-3-stephen@networkplumber.org> <216dfffb-2a50-3288-27a5-5078ea9eb22d@huawei.com> <20230307080657.4b7be99e@hermes.local> <2f046d72-355a-93a5-ede6-0f729e9e525b@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 Wed, 8 Mar 2023 08:36:48 +0800 fengchengwen wrote: > On 2023/3/8 0:06, Stephen Hemminger wrote: > > On Tue, 7 Mar 2023 17:35:32 +0800 > > fengchengwen wrote: > > > >> The syslog will add timestamp, but the syslog backend will re-write timestamp, so > >> in the last, you can't find the real-timestamp of this log print. sometimes it requires > >> to get real log time. > >> PS: we found it in our test environment because RR schedule hang too long (similar question > >> also found: https://bugzilla.redhat.com/show_bug.cgi?id=1855447). > >> > >> So suggest add timestamp in syslog string also, and don't convert to monotonic and just > >> print as normal format (just like syslog). > > > > > > Are you using systemd? > > Yes There is redhat bug about this: https://bugzilla.redhat.com/show_bug.cgi?id=991678 > > Never, never configure a DPDK application with real-time process priority. > > Polling model and RT don't mix. > > Maybe we should document them ? Part of previous discussion here: https://mails.dpdk.org/archives/dev/2021-April/203778.html In my experience running DPDK on isolated threads (cgroup or scheduler isolation) combined with remapping interrupts gives best response without lockup. I.e don't depend on scheduler to do the right thing. Instead ensure that each thread runs on dedicated CPU.