From: Jens Axboe <axboe@kernel.dk>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Tejun Heo <tj@kernel.org>, Shaohua Li <shli@fb.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RESEND] blkcg: simplify statistic accumulation code
Date: Tue, 16 Jan 2018 08:56:25 -0700 [thread overview]
Message-ID: <97f406a5-ca2c-43a4-d7a1-e6cf40b7a917@kernel.dk> (raw)
In-Reply-To: <20180116150154.2538110-1-arnd@arndb.de>
On 1/16/18 8:01 AM, Arnd Bergmann wrote:
> Some older compilers (gcc-4.4 through 4.6 in particular) struggle
> with the way that blkg_rwstat_read() returns a structure, leading
> to excessive stack usage and rather inefficient code:
>
> block/blk-cgroup.c: In function 'blkg_destroy':
> block/blk-cgroup.c:354:1: error: the frame size of 1296 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]
> block/cfq-iosched.c: In function 'cfqg_stats_add_aux':
> block/cfq-iosched.c:753:1: error: the frame size of 1928 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]
> block/bfq-cgroup.c: In function 'bfqg_stats_add_aux':
> block/bfq-cgroup.c:299:1: error: the frame size of 1928 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]
>
> I also notice that there is no point in using atomic accesses
> for the local variables, so storing the temporaries in simple 'u64'
> variables not only avoids the stack usage on older compilers but
> also improves the object code on modern versions.
Added for 4.16, thanks Arnd.
--
Jens Axboe
prev parent reply other threads:[~2018-01-16 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 15:01 Arnd Bergmann
2018-01-16 15:56 ` Jens Axboe [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=97f406a5-ca2c-43a4-d7a1-e6cf40b7a917@kernel.dk \
--to=axboe@kernel.dk \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=shli@fb.com \
--cc=tj@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
all inboxes | Powered by JetHome®