From: linas@austin.ibm.com
To: Greg KH <greg@kroah.com>
Cc: inuxppc64-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org,
pcihpd-discuss@lists.sourceforge.net
Subject: [PATCH] 2.6 RPAPHP structure size/performance
Date: Fri, 2 Jul 2004 11:21:54 -0500 [thread overview]
Message-ID: <20040702112154.O21634@forte.austin.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
Hi Greg,
Please review and apply the following patch if you find it agreeable.
This patch does not make any functional changes, but does improve
both performance and memory usage by rearranging structure elements.
The need for these changes became appearent during a code review of
the disassembly involving this structure. The memory footprint of this
structure is made smaller by grouping the byte fields next to each other.
The access of the list_head can be simplified by making it the first element
of the structure, thus avoiding a needless add-immediate without negatively
impacting any of the other accesses.
Signed-off-by: Linas Vepstas <linas@linas.org>
--linas
[-- Attachment #2: rpaphp.h.patch --]
[-- Type: text/plain, Size: 927 bytes --]
--- drivers/pci/hotplug/rpaphp.h.orig 2004-06-18 16:10:47.000000000 -0500
+++ drivers/pci/hotplug/rpaphp.h 2004-06-23 13:28:20.000000000 -0500
@@ -85,6 +85,7 @@ struct rpaphp_pci_func {
* struct slot - slot information for each *physical* slot
*/
struct slot {
+ struct list_head rpaphp_slot_list;
int state;
u32 index;
u32 type;
@@ -92,6 +93,7 @@ struct slot {
char *name;
char *location;
u8 removable;
+ u8 dev_type; /* VIO or PCI */
struct device_node *dn; /* slot's device_node in OFDT */
/* dn has phb info */
struct pci_dev *bridge; /* slot's pci_dev in pci_devices */
@@ -99,9 +101,7 @@ struct slot {
struct list_head pci_funcs; /* pci_devs in PCI slot */
struct vio_dev *vio_dev; /* vio_dev in VIO slot */
} dev;
- u8 dev_type; /* VIO or PCI */
struct hotplug_slot *hotplug_slot;
- struct list_head rpaphp_slot_list;
};
extern struct hotplug_slot_ops rpaphp_hotplug_slot_ops;
next reply other threads:[~2004-07-02 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 16:21 linas [this message]
2004-07-02 20:56 ` Greg KH
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=20040702112154.O21634@forte.austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=greg@kroah.com \
--cc=inuxppc64-dev@lists.linuxppc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
/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®