public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Jackie Liu <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH v2] io_uring: reduced function parameter ctx if possible
Date: Fri, 8 Nov 2019 07:16:32 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 11/8/19 7:11 AM, Jens Axboe wrote:
> On 11/8/19 12:29 AM, Jackie Liu wrote:
>> Many times, the core of the function is req, and req has already set
>> req->ctx at initialization time, so there is no need to pass in from
>> outside.
>>
>> Cleanup, no function change.
> 
> I was curious if this patch netted us any improvements as well, but it
> actually blows up the text segment a lot on my laptop. Before the
> patch:
> 
>     text	   data	    bss	    dec	    hex	filename
>    87504	  17588	    256	 105348	  19b84	fs/io_uring.o
> 
> and after:
> 
>     text	   data	    bss	    dec	    hex	filename
>    99098	  17876	    256	 117230	  1c9ee	fs/io_uring.o
> 
> which seems really odd. I double checked just to be sure!
> 
> axboe@x1:~ $ gcc --version
> gcc (Ubuntu 9.2.1-17ubuntu1~18.04.1) 9.2.1 20191102

I took a look at the generated code, and it looks like it's just
enabling gcc to inline a lot more aggressively.

-- 
Jens Axboe


  reply	other threads:[~2019-11-08 14:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08  7:29 [PATCH v2] io_uring: reduced function parameter ctx if possible Jackie Liu
2019-11-08  9:00 ` Jackie Liu
2019-11-08  9:10   ` Bob Liu
     [not found]     ` <[email protected]>
2019-11-08  9:24       ` Jackie Liu
2019-11-08  9:35         ` Bob Liu
2019-11-08 14:11 ` Jens Axboe
2019-11-08 14:16   ` Jens Axboe [this message]
     [not found]     ` <[email protected]>
2019-11-08 14:39       ` Jens Axboe
     [not found]         ` <[email protected]>
2019-11-08 14:47           ` Jens Axboe

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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