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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 10 May 2007 22:59:28 +1000
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	hadi@...erus.ca
Cc:	davem@...emloft.net, herbert@...dor.apana.org.au,
	krkumar2@...ibm.com, netdev@...r.kernel.org
Subject: Re: [PATCH] sched: Optimize return value of qdisc_restart

jamal <hadi@...erus.ca> wrote:
> 
> Ok, see if this makes sense:
> 
> CPU0                 CPU1 (holding qdisc running)
>  .                    |
>  .                    |
>  .                    + grab qlock
>  .                    |
>  .                    | deq pkt
>  .                    + release qlock
>  .                    + grab txlock
>  .                    |  send pkt
>  .                    + release txlock
>  .                    + grab qlock
>   has pktX            | (NEW: qlen = 0); return 0 instead of -1
>   waiting for qlock   + release qlock

			This release qlock isn't in our source code :)

>  + grab qlock         |
>  |                    + find that return code is 0
>  | enq pkt X          + release qdisc running
>  |                    |
>  + release qlock      | ==> outta here
> 
> pkt X is stuck unless some event happens such as a new pkt arrival. 
> In other words it sits there for an indeterminate period.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ