netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geliang Tang <geliangtang@gmail.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Mat Martineau <mathew.j.martineau@linux.intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org, mptcp@lists.01.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mptcp: move pr_fmt defining to protocol.h
Date: Fri, 3 Apr 2020 19:49:01 +0800	[thread overview]
Message-ID: <20200403114901.GB10201@OptiPlex> (raw)
In-Reply-To: <9674b6ce-3888-557e-8f32-230671363903@tessares.net>

On Fri, Apr 03, 2020 at 12:29:27PM +0200, Matthieu Baerts wrote:
> Hi Geliang,
> 
> On 03/04/2020 09:57, Geliang Tang wrote:
> > Some of the mptcp logs didn't print out the format string "MPTCP":
> > 
> > [  129.185774] DSS
> > [  129.185774] data_fin=0 dsn64=1 use_map=1 ack64=1 use_ack=1
> > [  129.185774] data_ack=5481534886531492085
> > [  129.185775] data_seq=15725204003114694615 subflow_seq=1425409 data_len=5216
> > [  129.185776] subflow=0000000093526a92 fully established=1 seq=0:0 remaining=28
> > [  129.185776] MPTCP: msk=00000000d5a704a6 ssk=00000000b5aabc31 data_avail=0 skb=0000000088f05424
> > [  129.185777] MPTCP: seq=15725204003114694615 is64=1 ssn=1425409 data_len=5216 data_fin=0
> > [  129.185777] MPTCP: msk=00000000d5a704a6 ssk=00000000b5aabc31 status=0
> > [  129.185778] MPTCP: msk ack_seq=da3b25b9a233c2c7 subflow ack_seq=da3b25b9a233c2c7
> > [  129.185778] MPTCP: msk=00000000d5a704a6 ssk=00000000b5aabc31 data_avail=1 skb=000000000caed2cc
> > [  129.185779] subflow=0000000093526a92 fully established=1 seq=0:0 remaining=28
> > 
> > So this patch moves the pr_fmt defining from protocol.c to protocol.h, which
> > is included by all the C files. Then we can get the same format string
> > "MPTCP" in all mptcp logs like this:
> > 
> > [  141.854787] MPTCP: DSS
> > [  141.854788] MPTCP: data_fin=0 dsn64=1 use_map=1 ack64=1 use_ack=1
> > [  141.854788] MPTCP: data_ack=18028325517710311871
> > [  141.854788] MPTCP: data_seq=6163976859259356786 subflow_seq=3309569 data_len=8192
> > [  141.854789] MPTCP: msk=000000005847a66a ssk=0000000022469903 data_avail=0 skb=00000000dd95efc3
> > [  141.854789] MPTCP: seq=6163976859259356786 is64=1 ssn=3309569 data_len=8192 data_fin=0
> > [  141.854790] MPTCP: msk=000000005847a66a ssk=0000000022469903 status=0
> > [  141.854790] MPTCP: msk ack_seq=558ad84b9be1d162 subflow ack_seq=558ad84b9be1d162
> > [  141.854791] MPTCP: msk=000000005847a66a ssk=0000000022469903 data_avail=1 skb=000000000b8926f6
> > [  141.854791] MPTCP: subflow=00000000e4e4579c fully established=1 seq=0:0 remaining=28
> > [  141.854792] MPTCP: subflow=00000000e4e4579c fully established=1 seq=0:dcdf2f3b remaining=28
> 
> Good idea to uniform that.
> I think it can be useful for MPTCP devs to add a different prefix in each
> MPTCP .c files but this small improvement can be done later.
> 
> LGTM, thanks Geliang!
> 
> Reviewed-by: Matthieu Baerts <matthieu.baerts@tessares.net>

Hi Matthieu,

Thanks for your reply.

I have already resend this patch to you, patch v2, a better version, add
pr_fmt defines in each .c files.

-Geliang

      parent reply	other threads:[~2020-04-03 11:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03  7:57 [PATCH] mptcp: move pr_fmt defining to protocol.h Geliang Tang
2020-04-03  9:14 ` [PATCH v2] mptcp: add some missing pr_fmt defines Geliang Tang
2020-04-03 11:57   ` Matthieu Baerts
2020-04-03 23:06   ` David Miller
2020-04-03 10:29 ` [PATCH] mptcp: move pr_fmt defining to protocol.h Matthieu Baerts
2020-04-03 11:41   ` Geliang Tang
2020-04-03 11:49   ` Geliang Tang [this message]

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=20200403114901.GB10201@OptiPlex \
    --to=geliangtang@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathew.j.martineau@linux.intel.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.01.org \
    --cc=netdev@vger.kernel.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).