From: Bixuan Cui <cuibixuan@huawei.com>
To: David Miller <davem@davemloft.net>
Cc: <stephen@networkplumber.org>, <kuba@kernel.org>,
<linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <jdmason@kudzu.us>,
<christophe.jaillet@wanadoo.fr>, <john.wanghui@huawei.com>
Subject: Re: [PATCH v2] net: neterion: vxge: reduce stack usage in VXGE_COMPLETE_VPATH_TX
Date: Tue, 21 Jul 2020 20:34:20 +0800 [thread overview]
Message-ID: <16aa9f4a-583e-2fd1-c14f-a3b2a6228436@huawei.com> (raw)
In-Reply-To: <20200720.183849.626605331445628040.davem@davemloft.net>
On 2020/7/21 9:38, David Miller wrote:
> From: Bixuan Cui <cuibixuan@huawei.com>
> Date: Mon, 20 Jul 2020 09:58:39 +0800
>
>> Fix the warning: [-Werror=-Wframe-larger-than=]
>>
>> drivers/net/ethernet/neterion/vxge/vxge-main.c:
>> In function'VXGE_COMPLETE_VPATH_TX.isra.37':
>> drivers/net/ethernet/neterion/vxge/vxge-main.c:119:1:
>> warning: the frame size of 1056 bytes is larger than 1024 bytes
>>
>> Dropping the NR_SKB_COMPLETED to 16 is appropriate that won't
>> have much impact on performance and functionality.
>>
>> Signed-off-by: Bixuan Cui <cuibixuan@huawei.com>
>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>> ---
>> v2: Dropping the NR_SKB_COMPLETED to 16.
> Applied.
thanks.
prev parent reply other threads:[~2020-07-21 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 17:32 [PATCH] net: neterion: vxge: reduce stack usage in VXGE_COMPLETE_VPATH_TX Bixuan Cui
2020-07-16 9:46 ` Joe Perches
2020-07-16 9:59 ` Bixuan Cui
2020-07-16 11:20 ` kernel test robot
2020-07-16 14:11 ` kernel test robot
2020-07-19 17:05 ` Stephen Hemminger
2020-07-20 1:57 ` Bixuan Cui
2020-07-20 1:58 ` [PATCH v2] " Bixuan Cui
2020-07-21 1:38 ` David Miller
2020-07-21 12:34 ` Bixuan Cui [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=16aa9f4a-583e-2fd1-c14f-a3b2a6228436@huawei.com \
--to=cuibixuan@huawei.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=jdmason@kudzu.us \
--cc=john.wanghui@huawei.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).