From: Denys Vlasenko <dvlasenk@redhat.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Denys Vlasenko <dvlasenk@redhat.com>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH] direct-io: Deinline dio_send_cur_page, save ~2000 bytes
Date: Sun, 13 Mar 2016 22:00:36 +0100 [thread overview]
Message-ID: <1457902836-30786-3-git-send-email-dvlasenk@redhat.com> (raw)
In-Reply-To: <1457902836-30786-1-git-send-email-dvlasenk@redhat.com>
This function compiles to 1070 bytes, 2 callsites
text data bss dec hex filename
9559 16 0 9575 2567 direct-io.o.before3
7587 16 0 7603 1db3 direct-io.o
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
CC: Al Viro <viro@zeniv.linux.org.uk>
CC: Jens Axboe <axboe@fb.com>
CC: Christoph Hellwig <hch@lst.de>
CC: linux-kernel@vger.kernel.org
---
fs/direct-io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/direct-io.c b/fs/direct-io.c
index 729c902..469baf7 100644
--- a/fs/direct-io.c
+++ b/fs/direct-io.c
@@ -710,7 +710,7 @@ static inline int dio_bio_add_page(struct dio_submit *sdio)
* The caller of this function is responsible for removing cur_page from the
* dio, and for dropping the refcount which came from that presence.
*/
-static inline int dio_send_cur_page(struct dio *dio, struct dio_submit *sdio,
+static int dio_send_cur_page(struct dio *dio, struct dio_submit *sdio,
struct buffer_head *map_bh)
{
int ret = 0;
--
1.8.1.4
next prev parent reply other threads:[~2016-03-13 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 21:00 [PATCH] direct-io: Deinline submit_page_section, save 5304 bytes Denys Vlasenko
2016-03-13 21:00 ` [PATCH] direct-io: Deinline dio_zero_block, save 2684 bytes Denys Vlasenko
2016-03-14 14:37 ` Jeff Moyer
2016-03-13 21:00 ` Denys Vlasenko [this message]
2016-03-14 14:37 ` [PATCH] direct-io: Deinline dio_send_cur_page, save ~2000 bytes Jeff Moyer
2016-03-14 14:36 ` [PATCH] direct-io: Deinline submit_page_section, save 5304 bytes Jeff Moyer
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=1457902836-30786-3-git-send-email-dvlasenk@redhat.com \
--to=dvlasenk@redhat.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).