Re: [PATCH 1/1] add configurable support for bridge forward delay

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Sun, Jan 24, 2010 at 5:13 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote:
> Hi Thomas,
>
>> I get your point, but what's your suggestion? The ioctl is marked
>> deprecated, too and the problem of setting the forward delay persists.
>> Would it suffer your needs if I got rid of libsysfs in general and
>> simply use the ioctl or is there a different replacement strategy you
>> prefer?
>
> if it has an ioctl, then use that one. I really don't understand why
> everybody things ioctl are bad. They work just fine and are often
> simpler to handle than sysfs files.

The documentation on
http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge
state:

"If the bridge is being used standalone (no other bridges near by).
Then it is safe to turn the forwarding delay off (set it to zero),
before adding interface to a bridge. Then you can run DHCP client
right away." Which I guess is what the PAN spec expects for a NAP
server, so perhaps having another entry in network.conf is not really
needed or only really useful for a GN server if someone is messing
with it e.g. mesh network, but even for that purpose it just seems
wrong to expect that in a fixed amount of time it will be able to
resolve the topology, so why bother?


-- 
Luiz Augusto von Dentz
Engenheiro de Computação
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux