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 E218E41E31; Thu, 9 Mar 2023 01:55:54 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BFACE40ED7; Thu, 9 Mar 2023 01:55:54 +0100 (CET) Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) by mails.dpdk.org (Postfix) with ESMTP id D62E340A7E for ; Thu, 9 Mar 2023 01:55:52 +0100 (CET) Received: from dggpeml500024.china.huawei.com (unknown [172.30.72.54]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4PX9dm5kJzznWp4; Thu, 9 Mar 2023 08:53:00 +0800 (CST) Received: from [10.67.100.224] (10.67.100.224) by dggpeml500024.china.huawei.com (7.185.36.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Thu, 9 Mar 2023 08:55:50 +0800 Subject: Re: [PATCH v3 2/2] eal: add option to put timestamp on console output To: Stephen Hemminger CC: , Bruce Richardson 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> <20230307180355.0a8443e9@hermes.local> From: fengchengwen Message-ID: <0139784b-f59d-a326-3b70-3098e952832b@huawei.com> Date: Thu, 9 Mar 2023 08:55:49 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <20230307180355.0a8443e9@hermes.local> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.100.224] X-ClientProxiedBy: dggems705-chm.china.huawei.com (10.3.19.182) To dggpeml500024.china.huawei.com (7.185.36.10) X-CFilter-Loop: Reflected 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 2023/3/8 10:03, Stephen Hemminger wrote: > 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. Got it, thanks. > > > > . >