From: Roland Dreier <rdreier@cisco.com>
To: "Bryan O'Sullivan" <bos@pathscale.com>
Cc: Greg KH <gregkh@suse.de>,
rolandd@cisco.com, akpm@osdl.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [PATCH 9 of 20] ipath - char devices for diagnostics and lightweight subnet management
Date: Fri, 10 Mar 2006 09:08:16 -0800 [thread overview]
Message-ID: <ada1wxab533.fsf@cisco.com> (raw)
In-Reply-To: <1141998230.28926.4.camel@localhost.localdomain> (Bryan O'Sullivan's message of "Fri, 10 Mar 2006 05:43:50 -0800")
Bryan> OK. What's a safe way to iterate over the devices in the
Bryan> presence of hotplug, then? I assume it's
Bryan> list_for_each_mumble; I just don't know what mumble is :-)
You need something that takes a reference to each device while you're
looking at it, like for_each_pci_dev(). But in general iterating
through devices is usually the wrong thing to do, because devices can
come and go in the middle of your loop. It's better to be driven by
the add and remove callbacks.
Bryan> No, ipath_max is updated any time a probe routine is
Bryan> called.
Yes, that's true. (BTW, what does making ipath_max an atomic_t get
you? The updates are protected by a lock anyway). But I was talking
about the code in ipath_verbs_init(), which is the only place you call
ipath_verbs_register() that I could find. You make one pass through
the devices that are present when ipath_verbs_init() is called at
module load time, and any devices that get added later are missed.
Similarly, if a device is unplugged while the verbs module is loaded,
there's no notification from the core driver of that, and you'll go
ahead and do ipath_verbs_unregister() on a device that is long gone
when you get to ipath_verbs_cleanup().
- R.
next prev parent reply other threads:[~2006-03-10 17:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eac2ad3017b5f160d24c.1141922822@localhost.localdomain>
2006-03-09 23:20 ` [PATCH 9 of 20] ipath - char devices for diagnostics and lightweight subnet management Roland Dreier
2006-03-09 23:39 ` Bryan O'Sullivan
2006-03-09 23:47 ` Roland Dreier
2006-03-09 23:50 ` Bryan O'Sullivan
2006-03-09 23:52 ` Roland Dreier
2006-03-10 15:54 ` Michael S. Tsirkin
2006-03-10 16:05 ` Bryan O'Sullivan
2006-03-09 23:24 ` Roland Dreier
2006-03-09 23:49 ` Bryan O'Sullivan
2006-03-09 23:51 ` Roland Dreier
2006-03-09 23:26 ` Roland Dreier
2006-03-09 23:52 ` Bryan O'Sullivan
2006-03-10 0:00 ` Roland Dreier
2006-03-10 0:04 ` Bryan O'Sullivan
2006-03-10 0:45 ` Greg KH
2006-03-10 0:48 ` Bryan O'Sullivan
2006-03-10 1:04 ` Greg KH
2006-03-10 4:41 ` Bryan O'Sullivan
2006-03-10 5:48 ` Greg KH
2006-03-10 13:40 ` Bryan O'Sullivan
2006-03-10 5:55 ` Roland Dreier
2006-03-10 13:43 ` Bryan O'Sullivan
2006-03-10 16:58 ` Greg KH
2006-03-10 17:05 ` Bryan O'Sullivan
2006-03-10 17:08 ` Roland Dreier [this message]
2006-03-10 17:32 ` Bryan O'Sullivan
2006-03-10 22:20 ` Roland Dreier
2006-03-10 0:35 [PATCH 0 of 20] [RFC] ipath driver - another round for review Bryan O'Sullivan
2006-03-10 0:35 ` [PATCH 9 of 20] ipath - char devices for diagnostics and lightweight subnet management Bryan O'Sullivan
2006-03-10 0:45 ` Roland Dreier
2006-03-10 0:47 ` Bryan O'Sullivan
2006-03-10 0:52 ` Roland Dreier
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=ada1wxab533.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=akpm@osdl.org \
--cc=bos@pathscale.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rolandd@cisco.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.