Home
last modified time | relevance | path

Searched hist:"346 cd5fe2d5056b424b28a67687c8dcd87624aca" (Results 1 – 3 of 3) sorted by relevance

/freebsd/sys/geom/
H A Dgeom_int.hdiff 346cd5fe2d5056b424b28a67687c8dcd87624aca Fri Sep 27 22:38:36 CEST 2002 Poul-Henning Kamp <phk@FreeBSD.org> Implement g_call_me() as a way for geom methods to schedule operations
to be performed in the event-thread.

To do this, we need to lock the eventlist with g_eventlock (nee g_doorlock),
since g_call_me() being called from the UP/DOWN paths will not be able to
aquire g_topology_lock.

This also means that for now these events are not referenced on any
particular consumer/provider/geom.

For UP/DOWN path use, this will not become a problem since the access()
function will make sure we drain any bio's before we dismantle.

Sponsored by: DARPA & NAI Labs.
diff 346cd5fe2d5056b424b28a67687c8dcd87624aca Fri Sep 27 22:38:36 CEST 2002 Poul-Henning Kamp <phk@FreeBSD.org> Implement g_call_me() as a way for geom methods to schedule operations
to be performed in the event-thread.

To do this, we need to lock the eventlist with g_eventlock (nee g_doorlock),
since g_call_me() being called from the UP/DOWN paths will not be able to
aquire g_topology_lock.

This also means that for now these events are not referenced on any
particular consumer/provider/geom.

For UP/DOWN path use, this will not become a problem since the access()
function will make sure we drain any bio's before we dismantle.

Sponsored by: DARPA & NAI Labs.
H A Dgeom_event.cdiff 346cd5fe2d5056b424b28a67687c8dcd87624aca Fri Sep 27 22:38:36 CEST 2002 Poul-Henning Kamp <phk@FreeBSD.org> Implement g_call_me() as a way for geom methods to schedule operations
to be performed in the event-thread.

To do this, we need to lock the eventlist with g_eventlock (nee g_doorlock),
since g_call_me() being called from the UP/DOWN paths will not be able to
aquire g_topology_lock.

This also means that for now these events are not referenced on any
particular consumer/provider/geom.

For UP/DOWN path use, this will not become a problem since the access()
function will make sure we drain any bio's before we dismantle.

Sponsored by: DARPA & NAI Labs.
diff 346cd5fe2d5056b424b28a67687c8dcd87624aca Fri Sep 27 22:38:36 CEST 2002 Poul-Henning Kamp <phk@FreeBSD.org> Implement g_call_me() as a way for geom methods to schedule operations
to be performed in the event-thread.

To do this, we need to lock the eventlist with g_eventlock (nee g_doorlock),
since g_call_me() being called from the UP/DOWN paths will not be able to
aquire g_topology_lock.

This also means that for now these events are not referenced on any
particular consumer/provider/geom.

For UP/DOWN path use, this will not become a problem since the access()
function will make sure we drain any bio's before we dismantle.

Sponsored by: DARPA & NAI Labs.
H A Dgeom.hdiff 346cd5fe2d5056b424b28a67687c8dcd87624aca Fri Sep 27 22:38:36 CEST 2002 Poul-Henning Kamp <phk@FreeBSD.org> Implement g_call_me() as a way for geom methods to schedule operations
to be performed in the event-thread.

To do this, we need to lock the eventlist with g_eventlock (nee g_doorlock),
since g_call_me() being called from the UP/DOWN paths will not be able to
aquire g_topology_lock.

This also means that for now these events are not referenced on any
particular consumer/provider/geom.

For UP/DOWN path use, this will not become a problem since the access()
function will make sure we drain any bio's before we dismantle.

Sponsored by: DARPA & NAI Labs.
diff 346cd5fe2d5056b424b28a67687c8dcd87624aca Fri Sep 27 22:38:36 CEST 2002 Poul-Henning Kamp <phk@FreeBSD.org> Implement g_call_me() as a way for geom methods to schedule operations
to be performed in the event-thread.

To do this, we need to lock the eventlist with g_eventlock (nee g_doorlock),
since g_call_me() being called from the UP/DOWN paths will not be able to
aquire g_topology_lock.

This also means that for now these events are not referenced on any
particular consumer/provider/geom.

For UP/DOWN path use, this will not become a problem since the access()
function will make sure we drain any bio's before we dismantle.

Sponsored by: DARPA & NAI Labs.