From: Jason Gunthorpe <jgg@nvidia.com>
To: Joe Perches <joe@perches.com>
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
zyjzyj2000@gmail.com, dledford@redhat.com,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] RDMA/rxe: Make rxe_type_info static const
Date: Wed, 27 Oct 2021 13:55:42 -0300 [thread overview]
Message-ID: <20211027165542.GB644080@nvidia.com> (raw)
In-Reply-To: <166b715d71f98336e8ecab72b0dbdd266eee9193.camel@perches.com>
On Sun, Oct 24, 2021 at 10:13:14AM -0700, Joe Perches wrote:
> Make struct rxe_type_info static const and local to the only uses.
> Moves a bit of data to text.
>
> $ size drivers/infiniband/sw/rxe/rxe_pool.o* (defconfig w/ infiniband swe)
> text data bss dec hex filename
> 4456 12 0 4468 1174 drivers/infiniband/sw/rxe/rxe_pool.o.new
> 3817 652 0 4469 1175 drivers/infiniband/sw/rxe/rxe_pool.o.old
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
> drivers/infiniband/sw/rxe/rxe_pool.c | 28 ++++++++++++++++++----------
> drivers/infiniband/sw/rxe/rxe_pool.h | 14 --------------
> 2 files changed, 18 insertions(+), 24 deletions(-)
Applied to for-next, thanks
Jason
next prev parent reply other threads:[~2021-10-27 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 16:43 [PATCH 1/2] RDMA/rxe: Save a few bytes from struct rxe_pool Christophe JAILLET
2021-10-24 16:43 ` [PATCH 2/2] RDMA/rxe: Use 'bitmap_zalloc()' when applicable Christophe JAILLET
2021-10-24 17:30 ` Christophe JAILLET
2021-10-24 17:13 ` [PATCH] RDMA/rxe: Make rxe_type_info static const Joe Perches
2021-10-27 16:55 ` Jason Gunthorpe [this message]
2021-10-27 16:55 ` [PATCH 1/2] RDMA/rxe: Save a few bytes from struct rxe_pool Jason Gunthorpe
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=20211027165542.GB644080@nvidia.com \
--to=jgg@nvidia.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dledford@redhat.com \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=zyjzyj2000@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.