lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 01 Sep 2014 14:56:46 -0700 (PDT) From: David Miller <davem@...emloft.net> To: hannes@...essinduktion.org Cc: netdev@...r.kernel.org, therbert@...gle.com, jhs@...atatu.com, edumazet@...gle.com, jeffrey.t.kirsher@...el.com, rusty@...tcorp.com.au, dborkman@...hat.com, brouer@...hat.com, john.r.fastabend@...el.com Subject: Re: [PATCH 0/2] Get rid of ndo_xmit_flush From: Hannes Frederic Sowa <hannes@...essinduktion.org> Date: Mon, 01 Sep 2014 22:05:42 +0200 > But as soon as we try to make Qdiscs absolutely lockless, we don't have > any guard that we don't concurrently dequeue skbs from it and suddenly > one Qdisc dequeue processing entity couldn't notify the driver that the > end of the batching was reached. I think this could become a problem > depending on how much of the locking is removed? I am certain that batching will require taking the device transmit lock over the ->ndo_start_xmit() invocations, and therefore the deferral decisions must atomically be made inside of that context. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists