From: David Miller <davem@davemloft.net>
To: cera@cera.cz
Cc: netdev@vger.kernel.org, sathya.perla@broadcom.com,
sriharsha.basavapatna@broadcom.com
Subject: Re: [PATCH net-next v2 0/8] be2net: small structures clean-up
Date: Thu, 12 Jul 2018 00:03:44 -0700 (PDT) [thread overview]
Message-ID: <20180712.000344.2226058838498782467.davem@davemloft.net> (raw)
In-Reply-To: <20180710205948.10574-1-cera@cera.cz>
From: Ivan Vecera <cera@cera.cz>
Date: Tue, 10 Jul 2018 22:59:40 +0200
> The series:
> - removes unused / unneccessary fields in several be2net structures
> - re-order fields in some structures to eliminate holes, cache-lines
> crosses
> - as result reduces size of main struct be_adapter by 4kB
Series applied, thanks.
prev parent reply other threads:[~2018-07-12 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 20:59 [PATCH net-next v2 0/8] be2net: small structures clean-up Ivan Vecera
2018-07-10 20:59 ` [PATCH net-next v2 1/8] be2net: remove unused old AIC info Ivan Vecera
2018-07-10 20:59 ` [PATCH net-next v2 2/8] be2net: remove unused old custom busy-poll fields Ivan Vecera
2018-07-10 20:59 ` [PATCH net-next v2 3/8] be2net: remove desc field from be_eq_obj Ivan Vecera
2018-07-10 20:59 ` [PATCH net-next v2 4/8] be2net: reorder fields in be_eq_obj structure Ivan Vecera
2018-07-10 20:59 ` [PATCH net-next v2 5/8] be2net: move txcp field in be_tx_obj to eliminate holes in the struct Ivan Vecera
2018-07-10 20:59 ` [PATCH net-next v2 6/8] be2net: remove unused tx_jiffies field from be_tx_stats Ivan Vecera
2018-07-10 20:59 ` [PATCH net-next v2 7/8] be2net: re-order fields in be_error_recovert to avoid hole Ivan Vecera
2018-07-10 20:59 ` [PATCH net-next v2 8/8] be2net: move rss_flags field in rss_info to ensure proper alignment Ivan Vecera
2018-07-12 7:03 ` 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=20180712.000344.2226058838498782467.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cera@cera.cz \
--cc=netdev@vger.kernel.org \
--cc=sathya.perla@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.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 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).