From: David Miller <davem@davemloft.net>
To: dvlasenk@redhat.com
Cc: alexei.starovoitov@gmail.com, alexander.duyck@gmail.com,
joe@perches.com, jpirko@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] net: deinline netif_tx_stop_all_queues(), remove WARN_ON in netif_tx_stop_queue()
Date: Tue, 12 May 2015 23:05:58 -0400 (EDT) [thread overview]
Message-ID: <20150512.230558.437567720437090973.davem@davemloft.net> (raw)
In-Reply-To: <1431371873-26969-1-git-send-email-dvlasenk@redhat.com>
From: Denys Vlasenko <dvlasenk@redhat.com>
Date: Mon, 11 May 2015 21:17:53 +0200
> These functions compile to 60 bytes of machine code each.
> With this .config: http://busybox.net/~vda/kernel_config
> there are 617 calls of netif_tx_stop_queue()
> and 49 calls of netif_tx_stop_all_queues() in vmlinux.
>
> To fix this, remove WARN_ON in netif_tx_stop_queue()
> as suggested by davem, and deinline netif_tx_stop_all_queues().
>
> Change in code size is about 20k:
>
> text data bss dec hex filename
> 82426986 22255416 20627456 125309858 77813a2 vmlinux.before
> 82406248 22255416 20627456 125289120 777c2a0 vmlinux
>
> gcc-4.7.2 still creates deinlined version of netif_tx_stop_queue
> sometimes:
>
> $ nm --size-sort vmlinux | grep netif_tx_stop_queue | wc -l
> 190
>
> ffffffff81b558a8 <netif_tx_stop_queue>:
> ffffffff81b558a8: 55 push %rbp
> ffffffff81b558a9: 48 89 e5 mov %rsp,%rbp
> ffffffff81b558ac: f0 80 8f e0 01 00 00 lock orb $0x1,0x1e0(%rdi)
> ffffffff81b558b3: 01
> ffffffff81b558b4: 5d pop %rbp
> ffffffff81b558b5: c3 retq
>
> This needs additional fixing.
>
> Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
Applied, thank you.
prev parent reply other threads:[~2015-05-13 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 19:17 [PATCH] net: deinline netif_tx_stop_all_queues(), remove WARN_ON in netif_tx_stop_queue() Denys Vlasenko
2015-05-12 16:00 ` Alexei Starovoitov
2015-05-13 3:05 ` David Miller [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=20150512.230558.437567720437090973.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.duyck@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=joe@perches.com \
--cc=jpirko@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.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;
as well as URLs for NNTP newsgroup(s).