linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Menglong Dong <menglong8.dong@gmail.com>
To: Jon Maloy <jmaloy@redhat.com>
Cc: ying.xue@windriver.com, David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	tipc-discussion@lists.sourceforge.net,
	Menglong Dong <dong.menglong@zte.com.cn>,
	Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH net-next] net: tipc: fix FB_MTU eat two pages
Date: Sun, 6 Jun 2021 22:40:49 +0800	[thread overview]
Message-ID: <CADxym3a_iTXWWOxK1vfNxuWRh7ve4vOWZERho7jTVUkxc2Z_rQ@mail.gmail.com> (raw)
In-Reply-To: <998cce2c-b18d-59c1-df64-fc62856c63a1@redhat.com>

On Sat, Jun 5, 2021 at 10:25 PM Jon Maloy <jmaloy@redhat.com> wrote:
>
>
>
> On 6/4/21 9:28 PM, Menglong Dong wrote:
> > Hello Maloy,
> >
> > On Sat, Jun 5, 2021 at 3:20 AM Jon Maloy <jmaloy@redhat.com> wrote:
> >>
> > [...]
> >> Please don't add any extra file just for this little fix. We have enough
> >> files.
> >> Keep the macros in msg.h/c where they used to be.  You can still add
> >> your copyright line to those files.
> >> Regarding the macros kept inside msg.c, they are there because we design
> >> by the principle of minimal exposure, even among our module internal files.
> >> Otherwise it is ok.
> >>
> > I don't want to add a new file too, but I found it's hard to define FB_MTU. I
> > tried to define it in msg.h, and 'crypto.h' should be included, which
> > 'BUF_HEADROOM' is defined in. However, 'msg.h' is already included in
> > 'crypto.h', so it doesn't work.
> >
> > I tried to define FB_MTU in 'crypto.h', but it feels weird to define
> > it here. And
> > FB_MTU is also used in 'bcast.c', so it can't be defined in 'msg.c'.
> >
> > I will see if there is a better solution.
> I think we can leverage the fact that this by definition is a node local
> message, and those are never encrypted.
> So, if you base FB_MTU on the non-crypto versions of BUF_HEADROOM and
> BUF_TAILROOM we should be safe.
> That will even give us better utilization of the space available.
>

Ok, that sounds nice. I'll make a V2 based on that.

Thanks!
Menglong Dong

  reply	other threads:[~2021-06-06 14:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04  7:44 [PATCH net-next] net: tipc: fix FB_MTU eat two pages menglong8.dong
2021-06-04 19:20 ` Jon Maloy
2021-06-05  1:28   ` Menglong Dong
2021-06-05 14:25     ` Jon Maloy
2021-06-06 14:40       ` Menglong Dong [this message]
2021-06-07 12:51       ` Menglong Dong
2021-06-08 22:37         ` Jon Maloy
2021-06-09  2:54           ` Menglong Dong
2021-06-09  7:34             ` Jon Maloy
2021-06-09 10:53               ` Menglong Dong

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=CADxym3a_iTXWWOxK1vfNxuWRh7ve4vOWZERho7jTVUkxc2Z_rQ@mail.gmail.com \
    --to=menglong8.dong@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dong.menglong@zte.com.cn \
    --cc=jmaloy@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=ying.xue@windriver.com \
    --cc=zealci@zte.com.cn \
    /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).