From: Arnd Bergmann <arnd@arndb.de>
To: Leon Romanovsky <leon@kernel.org>
Cc: Saeed Mahameed <saeedm@mellanox.com>,
"David S. Miller" <davem@davemloft.net>,
Moshe Shemesh <moshe@mellanox.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Networking <netdev@vger.kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net/mlx5: reduce stack usage in qp_read_field
Date: Mon, 4 May 2020 17:41:56 +0200 [thread overview]
Message-ID: <CAK8P3a30Qe=_L0Ji9k14SwGEZAKUX5FJ5YsFACGz_X3oBSSNQQ@mail.gmail.com> (raw)
In-Reply-To: <20200503053005.GC111287@unreal>
On Sun, May 3, 2020 at 7:30 AM Leon Romanovsky <leon@kernel.org> wrote:
> On Thu, Apr 30, 2020 at 04:37:14PM +0200, Arnd Bergmann wrote:
> > On Thu, Apr 30, 2020 at 7:22 AM Leon Romanovsky <leon@kernel.org> wrote:
> >
> > While warning limit is generally 1024 bytes for 32-bit architectures,
> > and 2048 bytes fro 64-bit architectures, we should probably
> > reduce the latter to something like 1280 bytes and fix up the
> > warnings that introduces.
>
> It a chicken and an egg problem, I tried to use default frame size, but
> the output of my kernel build was constantly flooded with those warnings
> and made hard to spot real issues in the code I developed.
>
When did you last try? I usually send patches whenever I see a new
warning, so there really shouldn't be any such warnings in the mainline
kernel except for cases where patches are still under discussion.
If you have a configuration in which you see lots of frame size warnings,
can you send me that .config file for that? It is possible that one or
more of the patches in my backlog fix a bunch of those issues
and need to be resent.
Arnd
next prev parent reply other threads:[~2020-05-04 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 21:23 [PATCH] net/mlx5: reduce stack usage in qp_read_field Arnd Bergmann
2020-04-28 21:44 ` Saeed Mahameed
2020-04-30 5:21 ` Leon Romanovsky
2020-04-30 14:37 ` Arnd Bergmann
2020-05-03 5:30 ` Leon Romanovsky
2020-05-04 15:41 ` Arnd Bergmann [this message]
2020-05-05 6:10 ` Leon Romanovsky
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='CAK8P3a30Qe=_L0Ji9k14SwGEZAKUX5FJ5YsFACGz_X3oBSSNQQ@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
/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).