From: Jeff Garzik <jgarzik@pobox.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [RFC] netdevice ops
Date: Fri, 18 May 2007 00:54:13 -0400 [thread overview]
Message-ID: <464D3175.8050007@pobox.com> (raw)
In-Reply-To: <20070517210737.17d88401@localhost>
Stephen Hemminger wrote:
> I want to take all the function pointers of 'struct net_device' and
> move them to 'struct net_device_ops'. This will save memory for the
> case of lots of devices, as well as reduce initialization code.
It will also add an additional deref to every operation, right?
Jeff
next prev parent reply other threads:[~2007-05-18 4:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 4:07 [RFC] netdevice ops Stephen Hemminger
2007-05-18 4:23 ` Ben Greear
2007-05-18 4:49 ` David Miller
2007-05-18 6:42 ` Ben Greear
2007-05-18 4:50 ` David Miller
2007-05-18 4:54 ` Jeff Garzik [this message]
2007-05-18 5:05 ` David Miller
2007-05-18 5:58 ` Stephen Hemminger
2007-05-19 14:18 ` Andi Kleen
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=464D3175.8050007@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).