From: Bjorn Helgaas <helgaas@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/2] PCI: Reorder some fields in 'struct pci_dev'
Date: Thu, 13 Jul 2023 11:24:19 -0500 [thread overview]
Message-ID: <20230713162419.GA321515@bhelgaas> (raw)
In-Reply-To: <407b17c3e56764ef2c558898d4ff4c6c04b2d757.1687105455.git.christophe.jaillet@wanadoo.fr>
On Sun, Jun 18, 2023 at 06:24:54PM +0200, Christophe JAILLET wrote:
> Group some bitfield variables to reduce hole.
> On x86_64, this shrinks the size of 'struct pci_dev' by 16 bytes when
> compiled with 'allmodconfig'. This goes from 3576 to 3560.
>
> The move related to CONFIG_PCIEASPM depends on the config. But it gives
> the opportunity to merge to bitfields.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Both patches applies to pci/misc for v6.6, thanks!
> ---
> include/linux/pci.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index c69a2cc1f412..106754757279 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -366,8 +366,8 @@ struct pci_dev {
> pci_power_t current_state; /* Current operating state. In ACPI,
> this is D0-D3, D0 being fully
> functional, and D3 being off. */
> - unsigned int imm_ready:1; /* Supports Immediate Readiness */
> u8 pm_cap; /* PM capability offset */
> + unsigned int imm_ready:1; /* Supports Immediate Readiness */
> unsigned int pme_support:5; /* Bitmask of states from which PME#
> can be generated */
> unsigned int pme_poll:1; /* Poll device's PME status bit */
> @@ -392,9 +392,9 @@ struct pci_dev {
>
> #ifdef CONFIG_PCIEASPM
> struct pcie_link_state *link_state; /* ASPM link state */
> + u16 l1ss; /* L1SS Capability pointer */
> unsigned int ltr_path:1; /* Latency Tolerance Reporting
> supported from root to here */
> - u16 l1ss; /* L1SS Capability pointer */
> #endif
> unsigned int pasid_no_tlp:1; /* PASID works without TLP Prefix */
> unsigned int eetlp_prefix_path:1; /* End-to-End TLP Prefix */
> --
> 2.34.1
>
prev parent reply other threads:[~2023-07-13 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 16:24 Christophe JAILLET
2023-06-18 16:24 ` [PATCH 2/2] PCI: Change the type of 'rom_attr_enabled' " Christophe JAILLET
2023-07-13 16:24 ` Bjorn Helgaas [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=20230713162419.GA321515@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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
all inboxes | Powered by JetHome®