* [Bridge] Bridge Control using sysfs and Spinlocks
@ 2005-10-18 12:23 Jonathan Chambers`
2005-10-18 16:42 ` Stephen Hemminger
0 siblings, 1 reply; 2+ messages in thread
From: Jonathan Chambers` @ 2005-10-18 12:23 UTC (permalink / raw)
To: bridge
I am attempting to change the bridge kernel module so that I have complete
control over the port states from user space via sysfs.
On code inspection I can see that whenever a reconfiguration of the bridge
itself is made, i.e. ageing time, forward delay, hello time, etc. then there
is a spin_lock_bh before the reconfiguration and a spin_unlock_bh after
reconfiguration.
However, when a reconfiguration of a bridge PORT is made e.g. path cost,
priority then the spin lock mechanism is not used. Is this correct
operation? (The old ioctl method uses spin locks on bridge port
reconfiguration, whereas I am reconfiguring via sysfs)
If I am to change the bridge module to accept requests to change the port
state should I be using the spin locks?
Thanks in advance
Jon Chambers.
_________________________________________________________________
MSN Messenger 7.5 is now out. Download it for FREE here.
http://messenger.msn.co.uk
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bridge] Bridge Control using sysfs and Spinlocks
2005-10-18 12:23 [Bridge] Bridge Control using sysfs and Spinlocks Jonathan Chambers`
@ 2005-10-18 16:42 ` Stephen Hemminger
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2005-10-18 16:42 UTC (permalink / raw)
To: Jonathan Chambers`; +Cc: bridge
On Tue, 18 Oct 2005 13:23:46 +0100
"Jonathan Chambers`" <chamber_j@hotmail.com> wrote:
> I am attempting to change the bridge kernel module so that I have complete
> control over the port states from user space via sysfs.
>
> On code inspection I can see that whenever a reconfiguration of the bridge
> itself is made, i.e. ageing time, forward delay, hello time, etc. then there
> is a spin_lock_bh before the reconfiguration and a spin_unlock_bh after
> reconfiguration.
Yes, makes sense to lock those operations. Looks like a simple oversight.
> However, when a reconfiguration of a bridge PORT is made e.g. path cost,
> priority then the spin lock mechanism is not used. Is this correct
> operation? (The old ioctl method uses spin locks on bridge port
> reconfiguration, whereas I am reconfiguring via sysfs)
>
> If I am to change the bridge module to accept requests to change the port
> state should I be using the spin locks?
>
> Thanks in advance
>
> Jon Chambers.
>
> _________________________________________________________________
> MSN Messenger 7.5 is now out. Download it for FREE here.
> http://messenger.msn.co.uk
>
--
Stephen Hemminger <shemminger@osdl.org>
OSDL http://developer.osdl.org/~shemminger
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-10-18 16:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-18 12:23 [Bridge] Bridge Control using sysfs and Spinlocks Jonathan Chambers`
2005-10-18 16:42 ` Stephen Hemminger
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.