From: Krzysztof Halasa <khc@pm.waw.pl>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org
Subject: Re: netdev->priv and netdev_priv(dev)
Date: Tue, 29 Jan 2008 22:52:02 +0100 [thread overview]
Message-ID: <m3bq74uwot.fsf@maximus.localdomain> (raw)
In-Reply-To: <20080129124259.7c502d13@deepthought> (Stephen Hemminger's message of "Tue\, 29 Jan 2008 12\:42\:59 -0800")
Stephen Hemminger <shemminger@linux-foundation.org> writes:
> Those drivers were making a incorrect assumption and should be fixed.
> The in-tree drivers were fixed when this was done. If you have an out
> of tree driver, then too bad for you.
I have few out-of-tree drivers (IOW not yet merged) but they aren't
affected. These in the tree are (actually I was contacted by driver's
author and am considering the best way to fix this).
> The additional overhead of the address calculation would slow down the
> well behaved drivers.
There is always dev->priv.
> There was discussion of alternative layouts of
> the network device allocation or limiting the number of subqueue's so
> that netdev_priv could be a simple addition again, but nothing came of
> it.
This isn't about an addition, netdev_priv() is still there. The
semantics silently changed, that's it.
I'm fine with its removal, is it ok? The trivial "return dev->priv"
isn't worth it anyway.
--
Krzysztof Halasa
prev parent reply other threads:[~2008-01-29 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 20:10 netdev->priv and netdev_priv(dev) Krzysztof Halasa
2008-01-29 20:42 ` Stephen Hemminger
2008-01-29 21:52 ` Krzysztof Halasa [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=m3bq74uwot.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--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).