From: Thomas Graf <tgraf@suug.ch>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 0/3 net-next] Bring sizeof(net_device) down to < 2K bytes
Date: Fri, 10 Apr 2015 01:43:25 +0200 [thread overview]
Message-ID: <cover.1428622095.git.tgraf@suug.ch> (raw)
The size of struct net_device crossed the 2K boundary a while ago which
is a waste in combination with many net namespaces. This series brings
the size of struct net_device down to well below 2K in total size with
a typical configuration. Some reserves a several holes leave room for
further expansion.
Thomas Graf (3):
e1000: Allocate pm_qos_req as needed
net_device: Reorder members to fill holes
net_device: Add minimal padding to allow for net_device pointer
alignment
drivers/net/ethernet/intel/e1000e/netdev.c | 15 ++++++++---
include/linux/kernel.h | 2 ++
include/linux/netdevice.h | 41 ++++++++++++++----------------
net/core/dev.c | 3 +--
4 files changed, 33 insertions(+), 28 deletions(-)
--
@Jeff: I only boot tested the e1000 in a virtual machine.
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Graf <tgraf@suug.ch>
To: davem@davemloft.net
Cc: jeffrey.t.kirsher@intel.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: [PATCH 0/3 net-next] Bring sizeof(net_device) down to < 2K bytes
Date: Fri, 10 Apr 2015 01:43:25 +0200 [thread overview]
Message-ID: <cover.1428622095.git.tgraf@suug.ch> (raw)
The size of struct net_device crossed the 2K boundary a while ago which
is a waste in combination with many net namespaces. This series brings
the size of struct net_device down to well below 2K in total size with
a typical configuration. Some reserves a several holes leave room for
further expansion.
Thomas Graf (3):
e1000: Allocate pm_qos_req as needed
net_device: Reorder members to fill holes
net_device: Add minimal padding to allow for net_device pointer
alignment
drivers/net/ethernet/intel/e1000e/netdev.c | 15 ++++++++---
include/linux/kernel.h | 2 ++
include/linux/netdevice.h | 41 ++++++++++++++----------------
net/core/dev.c | 3 +--
4 files changed, 33 insertions(+), 28 deletions(-)
--
@Jeff: I only boot tested the e1000 in a virtual machine.
next reply other threads:[~2015-04-09 23:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 23:43 Thomas Graf [this message]
2015-04-09 23:43 ` [PATCH 0/3 net-next] Bring sizeof(net_device) down to < 2K bytes Thomas Graf
2015-04-09 23:43 ` [Intel-wired-lan] [PATCH 1/3 net-next] e1000: Allocate pm_qos_req as needed Thomas Graf
2015-04-09 23:43 ` Thomas Graf
2015-04-10 0:08 ` [Intel-wired-lan] " Jeff Kirsher
2015-04-10 0:08 ` Jeff Kirsher
2015-04-10 4:35 ` [Intel-wired-lan] " Jeff Kirsher
2015-04-10 4:35 ` Jeff Kirsher
2015-04-10 8:01 ` Daniel Borkmann
2015-04-10 8:01 ` Daniel Borkmann
2015-04-10 8:48 ` Thomas Graf
2015-04-10 8:48 ` Thomas Graf
2015-04-10 8:58 ` Jeff Kirsher
2015-04-10 8:58 ` Jeff Kirsher
2015-04-09 23:43 ` [Intel-wired-lan] [PATCH 2/3 net-next] net_device: Reorder members to fill holes Thomas Graf
2015-04-09 23:43 ` Thomas Graf
2015-04-09 23:43 ` [Intel-wired-lan] [PATCH 3/3 net-next] net_device: Add minimal padding to allow for net_device pointer alignment Thomas Graf
2015-04-09 23:43 ` Thomas Graf
2015-04-10 0:34 ` [Intel-wired-lan] " Eric Dumazet
2015-04-10 0:34 ` Eric Dumazet
2015-04-10 8:48 ` [Intel-wired-lan] " Thomas Graf
2015-04-10 8:48 ` Thomas Graf
2015-04-10 9:03 ` [Intel-wired-lan] " Eric Dumazet
2015-04-10 9:03 ` Eric Dumazet
2015-04-10 0:01 ` [Intel-wired-lan] [PATCH 0/3 net-next] Bring sizeof(net_device) down to < 2K bytes Alexei Starovoitov
2015-04-10 0:01 ` Alexei Starovoitov
2015-04-10 8:41 ` [Intel-wired-lan] " Thomas Graf
2015-04-10 8:41 ` Thomas Graf
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=cover.1428622095.git.tgraf@suug.ch \
--to=tgraf@suug.ch \
--cc=intel-wired-lan@osuosl.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 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.