-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I'm writing a network driver that requires a bit of work to be done before packets can start being transmitted. On device open, the kernel module notifies a worker in userspace that the device has been started, the worker performs startup tasks, and notifies the kernel module that startup is complete, after which the module calls netif_start_queue to allow packets to come into the module. In theory.. In reality, as soon as 'open' happens, packets immediately start appearing for transmission at hard_start_xmit (presumably IPv6's router discovery). At the moment I've got a hack that just queues outgoing packets until the device is started, but that isn't really acceptable. Does anyone have any clue why this is happening, and how it can be prevented? Cheers =) Mike - -- Mike Tyson <mike@xxxxxxxxxxx> M: (+61) 0407 754 124 W: http://mike.tyson.id.au B: http://mike.tyson.id.au/blog -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDSGUq/eih+gEb7pQRAqx0AKCLEkm2wzTTA2sTT6dyA8jlp7D8eQCfZbDf Cr5v5aApHaCdsPsmO7zyLy4= =zZ2D -----END PGP SIGNATURE----- -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
