DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chaoyong He <chaoyong.he@corigine.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	oss-drivers <oss-drivers@corigine.com>,
	Long Wu <Long.Wu@nephogine.com>,
	Nole Zhang <peng.zhang@corigine.com>
Subject: RE: [PATCH v2 05/11] net/nfp: adjust the log statement
Date: Thu, 12 Oct 2023 01:40:52 +0000	[thread overview]
Message-ID: <SJ0PR13MB55450F6D1C1D383F4886578E9ED3A@SJ0PR13MB5545.namprd13.prod.outlook.com> (raw)
In-Reply-To: <20231011183855.2d97c582@hermes.local>



> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Thursday, October 12, 2023 9:39 AM
> To: Chaoyong He <chaoyong.he@corigine.com>
> Cc: dev@dpdk.org; oss-drivers <oss-drivers@corigine.com>; Long Wu
> <Long.Wu@nephogine.com>; Nole Zhang <peng.zhang@corigine.com>
> Subject: Re: [PATCH v2 05/11] net/nfp: adjust the log statement
> 
> On Thu, 12 Oct 2023 09:26:58 +0800
> Chaoyong He <chaoyong.he@corigine.com> wrote:
> 
> > +			PMD_RX_LOG(ERR, "mbuf overflow likely due to the
> RX offset.\n"
> > +					"\t\tYour mbuf size should have extra
> space for"
> > +					" RX offset=%u bytes.\n"
> > +					"\t\tCurrently you just have %u bytes
> available"
> > +					" but the received packet is %u bytes
> long",
> > +					hw->rx_offset,
> > +					rxq->mbuf_size - hw->rx_offset,
> > +					mb->data_len);
> 
> Multi-line log messages with tabs look good on command line (developer) but
> don't work well when application is run as a service and logging is going to
> syslog.
> Syslog doesn't like messages with newlines in them.
> The message is way to long. Make it shorter, and put any other notes in a
> comment please..

Thanks, got it.
I will revise as you said in the next version.

  reply	other threads:[~2023-10-12  1:40 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-07  2:33 [PATCH 00/11] Unify the PMD coding style Chaoyong He
2023-10-07  2:33 ` [PATCH 01/11] net/nfp: explicitly compare to null and 0 Chaoyong He
2023-10-07  2:33 ` [PATCH 02/11] net/nfp: unify the indent coding style Chaoyong He
2023-10-07  2:33 ` [PATCH 03/11] net/nfp: unify the type of integer variable Chaoyong He
2023-10-07  2:33 ` [PATCH 04/11] net/nfp: standard the local variable coding style Chaoyong He
2023-10-07  2:33 ` [PATCH 05/11] net/nfp: adjust the log statement Chaoyong He
2023-10-07  2:33 ` [PATCH 06/11] net/nfp: standard the comment style Chaoyong He
2023-10-07  2:33 ` [PATCH 07/11] net/nfp: standard the blank character Chaoyong He
2023-10-07  2:33 ` [PATCH 08/11] net/nfp: unify the guide line of header file Chaoyong He
2023-10-07  2:33 ` [PATCH 09/11] net/nfp: rename some parameter and variable Chaoyong He
2023-10-07  2:33 ` [PATCH 10/11] net/nfp: adjust logic to make it more readable Chaoyong He
2023-10-07  2:33 ` [PATCH 11/11] net/nfp: refact the meson build file Chaoyong He
2023-10-12  1:26 ` [PATCH v2 00/11] Unify the PMD coding style Chaoyong He
2023-10-12  1:26   ` [PATCH v2 01/11] net/nfp: explicitly compare to null and 0 Chaoyong He
2023-10-12  1:26   ` [PATCH v2 02/11] net/nfp: unify the indent coding style Chaoyong He
2023-10-12  1:26   ` [PATCH v2 03/11] net/nfp: unify the type of integer variable Chaoyong He
2023-10-12  1:26   ` [PATCH v2 04/11] net/nfp: standard the local variable coding style Chaoyong He
2023-10-12  1:26   ` [PATCH v2 05/11] net/nfp: adjust the log statement Chaoyong He
2023-10-12  1:38     ` Stephen Hemminger
2023-10-12  1:40       ` Chaoyong He [this message]
2023-10-12  1:26   ` [PATCH v2 06/11] net/nfp: standard the comment style Chaoyong He
2023-10-12  1:27   ` [PATCH v2 07/11] net/nfp: standard the blank character Chaoyong He
2023-10-12  1:27   ` [PATCH v2 08/11] net/nfp: unify the guide line of header file Chaoyong He
2023-10-12  1:27   ` [PATCH v2 09/11] net/nfp: rename some parameter and variable Chaoyong He
2023-10-12  1:27   ` [PATCH v2 10/11] net/nfp: adjust logic to make it more readable Chaoyong He
2023-10-12  1:27   ` [PATCH v2 11/11] net/nfp: refact the meson build file Chaoyong He
2023-10-13  6:06   ` [PATCH v3 00/11] Unify the PMD coding style Chaoyong He
2023-10-13  6:06     ` [PATCH v3 01/11] net/nfp: explicitly compare to null and 0 Chaoyong He
2023-10-13  6:06     ` [PATCH v3 02/11] net/nfp: unify the indent coding style Chaoyong He
2023-10-13  6:06     ` [PATCH v3 03/11] net/nfp: unify the type of integer variable Chaoyong He
2023-10-13  6:06     ` [PATCH v3 04/11] net/nfp: standard the local variable coding style Chaoyong He
2023-10-13  6:06     ` [PATCH v3 05/11] net/nfp: adjust the log statement Chaoyong He
2023-10-13  6:06     ` [PATCH v3 06/11] net/nfp: standard the comment style Chaoyong He
2023-10-13  6:06     ` [PATCH v3 07/11] net/nfp: standard the blank character Chaoyong He
2023-10-13  6:06     ` [PATCH v3 08/11] net/nfp: unify the guide line of header file Chaoyong He
2023-10-13  6:06     ` [PATCH v3 09/11] net/nfp: rename some parameter and variable Chaoyong He
2023-10-13  6:06     ` [PATCH v3 10/11] net/nfp: adjust logic to make it more readable Chaoyong He
2023-10-13  6:06     ` [PATCH v3 11/11] net/nfp: refact the meson build file Chaoyong He
2023-10-16 16:50       ` Ferruh Yigit
2023-10-16 16:50     ` [PATCH v3 00/11] Unify the PMD coding style Ferruh Yigit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ0PR13MB55450F6D1C1D383F4886578E9ED3A@SJ0PR13MB5545.namprd13.prod.outlook.com \
    --to=chaoyong.he@corigine.com \
    --cc=Long.Wu@nephogine.com \
    --cc=dev@dpdk.org \
    --cc=oss-drivers@corigine.com \
    --cc=peng.zhang@corigine.com \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).