From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 7D85341E0E;
	Wed,  8 Mar 2023 01:37:04 +0100 (CET)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 5F94540EF0;
	Wed,  8 Mar 2023 01:37:04 +0100 (CET)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188])
 by mails.dpdk.org (Postfix) with ESMTP id D4B0940ED6
 for <dev@dpdk.org>; Wed,  8 Mar 2023 01:37:02 +0100 (CET)
Received: from dggpeml500024.china.huawei.com (unknown [172.30.72.53])
 by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4PWYH805RQzKqHC;
 Wed,  8 Mar 2023 08:34:44 +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; Wed, 8 Mar 2023 08:36:48 +0800
Subject: Re: [PATCH v3 2/2] eal: add option to put timestamp on console output
To: Stephen Hemminger <stephen@networkplumber.org>
CC: <dev@dpdk.org>, Bruce Richardson <bruce.richardson@intel.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>
From: fengchengwen <fengchengwen@huawei.com>
Message-ID: <2f046d72-355a-93a5-ede6-0f729e9e525b@huawei.com>
Date: Wed, 8 Mar 2023 08:36:48 +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: <20230307080657.4b7be99e@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: dggems702-chm.china.huawei.com (10.3.19.179) 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 <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org



On 2023/3/8 0:06, Stephen Hemminger wrote:
> On Tue, 7 Mar 2023 17:35:32 +0800
> fengchengwen <fengchengwen@huawei.com> 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

> 
> Never, never configure a DPDK application with real-time process priority.
> Polling model and RT don't mix.

Maybe we should document them ?

> .
>