From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: Keith Owens <kaos@ocs.com.au>, Andi Kleen <ak@suse.de>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
"Hen, Shmulik" <shmulik.hen@intel.com>,
"'LKML'" <linux-kernel@vger.kernel.org>,
"'LNML'" <linux-net@vger.kernel.org>
Subject: Re: Locking Between User Context and Soft IRQs in 2.4.0
Date: Sun, 05 Nov 2000 21:20:12 -0500 [thread overview]
Message-ID: <3A06155C.796995DD@yahoo.com> (raw)
In-Reply-To: Your message of "Sun, 05 Nov 2000 14:39:43 +1100." <9277.973395583@ocs3.ocs-net> <9368.973396061@ocs3.ocs-net> <3A054872.8D88EF95@uow.edu.au>
Andrew Morton wrote:
> y'know, if we keep working this patch for about a year we
> might end up getting it right. Thousand monkeys and all that.
Yeah, probably still a year until the release of 2.4.0. 8)
Now where did I put those darn bananas...
> - With this patch applied, the module refcounts for netdevices
> will show doubled values in `lsmod', unless those drivers
> have been changed to remove the now unneeded MOD_INC/DEC_USE_COUNT
> macros (perhaps with the above 2.2-compatibility thing).
Assuming that nobody has all the MOD_..._USE_COUNT things culled
from a tree somewhere already, I quickly hacked up the following
script for drivers/net:
----------------
#!/bin/bash
for i in `grep -l 'MOD_..._USE_COUNT;' *.c */*.c`
do
mv $i $i~
cat $i~ | \
sed '/^$/{N;s/.*MOD.*COUNT;//;tz;b;:z;N;s/^\n$//;};/.*MOD.*COUNT;/d' > $i
done
----------------
It looks ugly but it zaps out the extra blank line when MOD_.*COUNT
had a blank line above and below. I had a quick look at the resulting
diff (4200 lines!) and it looks like the post-script hand editing will
be minimal (e.g. a few arcnet drivers have MOD_*_COUNT as the only code
in an if block).
We might want to filter the file list created by grep against VERSION_CODE
as people with that in their driver(s) probably don't want the wholesale
deletion of MOD_*_COUNT. (OTOH, drivers that have VERSION_CODE that
supports 2.0.38 or oddball 2.3.x versions could probably be pruned...)
That still leaves the addition of dev->owner = THIS_MODULE into
each device probe. One *hackish* way to do this without having to
deal with each driver could be something like this in netdevice.h
- extern void ether_setup(struct net_device *dev);
+ extern void __ether_setup(struct net_device *dev);
+ static inline void ether_setup(struct net_device *dev){
+ dev->owner = THIS_MODULE;
+ __ether_setup(dev);
+ }
Ugh. Probably should just add it to each probe and be done with it...
Paul. (aka. monkey #937)
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-06 8:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 14:10 Locking Between User Context and Soft IRQs in 2.4.0 Hen, Shmulik
2000-11-04 9:45 ` Jeff Garzik
2000-11-04 10:19 ` Andi Kleen
2000-11-04 15:36 ` Jeff Garzik
2000-11-04 16:56 ` Andi Kleen
2000-11-04 17:07 ` Jeff Garzik
2000-11-05 0:38 ` Andi Kleen
2000-11-05 1:28 ` Andrew Morton
2000-11-05 1:52 ` Andrew Morton
2000-11-05 2:32 ` Andi Kleen
2000-11-05 3:39 ` Keith Owens
2000-11-05 3:47 ` Keith Owens
2000-11-05 11:45 ` Andrew Morton
2000-11-06 2:20 ` Paul Gortmaker [this message]
2000-11-06 9:55 ` Andrew Morton
2000-11-06 10:05 ` Jeff Garzik
2000-11-06 12:37 ` Keith Owens
2000-11-06 12:49 ` Jeff Garzik
2000-11-06 12:58 ` Keith Owens
2000-11-06 13:09 ` Jeff Garzik
2000-11-06 13:18 ` Keith Owens
2000-11-07 2:23 ` Rusty Russell
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=3A06155C.796995DD@yahoo.com \
--to=p_gortmaker@yahoo.com \
--cc=ak@suse.de \
--cc=andrewm@uow.edu.au \
--cc=jgarzik@mandrakesoft.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=shmulik.hen@intel.com \
/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.