search for: starvation

Hi, I'v included speex-lib into my http://www.visit.se/~pointless IP-Sound streaming app. When using speex the sound is being garbled for short intervals, approx every 20:th second. Sounds like buffer starvation..... but in between it sounds 100% ok. As I am using other "codecs" with success there might be something that I have missed in the implementation of speex. Using version 1.1.8. Anyone have an idea about this? /Regards

Hello, If an ordinary user runs: -- snip -- cat > starv.c <<EOF main(){ char *point; while(1) { point = ( char * ) malloc(10000); }} EOF cc starv.c while true do ./a.out & done -- snip -- This will fast starv the operating system (FreeBSD 6.2). I have tried to limit the number of processes and the amount of memmory consumed (in login.conf). There is also a file /etc/malloc.conf

http://bugs.freedesktop.org/show_bug.cgi?id=16640 Summary: NV18/DVI bandwidth starvation issue Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: high Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: d.okias at...

Standard apology if old... This demonstrates a resource starvation attack on the setuid root passwd(1) program. In the case I tested it was the Red Hat Linux passwd-0.50-7 program without shadowing. #include <stdio.h> #include <sys/time.h> #include <stdlib.h> #include <unistd.h> #include <sys/resource.h> main () { struct rlimit rl,...

I think I''ve run into some kind of queue starvation bug w/ DRb - it normally takes minutes per item to process items in the queue, and normally the queue has a bit of a backlog. But when it''s empty (nothing coming in), it seems to stop checking for new work. Has anyone else run into this w/ DRb? Any suggestions for debugging this? Thank...

Hi! I was hoping to receive some help on a difficult matter - I have tried a lot already. http://stackoverflow.com/questions/12468781/rails-thread-starvation That''s the link, I hope it is ok to link there. Thanks! Carl -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To u...

....... hope someone can explain them to me... As I already told I have the following config : egress { class (30kbps) {sfq}; class (50kbps) {sfq}; class (80kbps) {sfq}; class (30kbps) {sfq}; class (50kbps) {sfq}; ...hundreds like this... class (10kbps,default) {sfq}; } What I got is traffic starvation very often for a period of ~30 sec.. as proposed I''ve done : egress { ...hundreds classes... class (10kbps, prio 7, default) {sfq}; } It seemed a litlle bit better the starvation seemed to be just ~10sec but this time happen much often... then I made a final touch : egress { ...hund...

...m is to allow unfair lock in a > para-virtualized environment. In this case, a new lock acquirer can > come and steal the lock if the next-in-line CPU to get the lock is > scheduled out. Unfair lock in a native environment is generally not a > good idea as there is a possibility of lock starvation for a heavily > contended lock. I'm not sure I'm keen on losing the fairness in PV environment. I'm concerned that on an over-committed host, the lock starvation problem will be particularly bad. But I'll have to revist this once a non-broken PV qspinlock implementation exists...

...m is to allow unfair lock in a > para-virtualized environment. In this case, a new lock acquirer can > come and steal the lock if the next-in-line CPU to get the lock is > scheduled out. Unfair lock in a native environment is generally not a > good idea as there is a possibility of lock starvation for a heavily > contended lock. I'm not sure I'm keen on losing the fairness in PV environment. I'm concerned that on an over-committed host, the lock starvation problem will be particularly bad. But I'll have to revist this once a non-broken PV qspinlock implementation exists...

...borrowing method on one device by itself, e.g. ppp0, alone using HTB or the like. this means that i have to create for another device, e.g. ppp1, its own HTB or CBQ tree. So, how can i in PPPoE technology setup sharing or borrowing between all the pppX devices so it won''t let network starvation problem float on surface? Thanks.

...stra wrote: > On Sat, Jun 28, 2014 at 02:47:04PM +0530, Raghavendra K T wrote: >> In virtualized environment there are mainly three problems >> related to spinlocks that affects performance. >> 1. LHP (lock holder preemption) >> 2. Lock Waiter Preemption (LWP) >> 3. Starvation/fairness >> >> Though Ticketlocks solve fairness problem it worsens LWP, LHP problems. Though >> pv-ticketlocks tried to address these problems we can further improve at the >> cost of relaxed fairness. The following patch tries to achieve that by grouping >> (batche...

...stra wrote: > On Sat, Jun 28, 2014 at 02:47:04PM +0530, Raghavendra K T wrote: >> In virtualized environment there are mainly three problems >> related to spinlocks that affects performance. >> 1. LHP (lock holder preemption) >> 2. Lock Waiter Preemption (LWP) >> 3. Starvation/fairness >> >> Though Ticketlocks solve fairness problem it worsens LWP, LHP problems. Though >> pv-ticketlocks tried to address these problems we can further improve at the >> cost of relaxed fairness. The following patch tries to achieve that by grouping >> (batche...

...) : defaults I configured PRIO qdisc on Router A''s outer interface to Router B. the results of test - TCP throughput about 80Mbps - UDP throughput about 900Mbps. (UDP try to send 1Gbps) First question: The TCP stream with higher priority than UDP stream with lower priority experienced starvation in stead of UDP stream. Is it correct? Did you test PRIO qdisc with TCP having high priority and UDP having low priority? In the below, there is my configuration. Is there something wrong? Second Question: When I test with one TCP stream having high priority and one TCP stream having low priorit...

In virtualized environment there are mainly three problems related to spinlocks that affects performance. 1. LHP (lock holder preemption) 2. Lock Waiter Preemption (LWP) 3. Starvation/fairness Though Ticketlocks solve fairness problem it worsens LWP, LHP problems. Though pv-ticketlocks tried to address these problems we can further improve at the cost of relaxed fairness. The following patch tries to achieve that by grouping (batched) ticketlocks. Here we form a batch of elig...

In virtualized environment there are mainly three problems related to spinlocks that affects performance. 1. LHP (lock holder preemption) 2. Lock Waiter Preemption (LWP) 3. Starvation/fairness Though Ticketlocks solve fairness problem it worsens LWP, LHP problems. Though pv-ticketlocks tried to address these problems we can further improve at the cost of relaxed fairness. The following patch tries to achieve that by grouping (batched) ticketlocks. Here we form a batch of elig...

...ash: SHA1 ============================================================================= FreeBSD-SA-03:14.arp Security Advisory The FreeBSD Project Topic: denial of service due to ARP resource starvation Category: core Module: sys Announced: 2003-09-25 Credits: Apple Product Security <product-security@apple.com> Affects: All releases of FreeBSD FreeBSD 4-STABLE prior to the correction date Corrected: 2003-09-24 21:48:00 UTC (RELENG_4, 4.9...

...me to time the traffic got "stalled". I tried numerous things to solve the problem - cable-wiring, different cards the problem still persist. My kernel is 2.4.20, as seen in the list I got the sch_htb.c from 2.4.22 kernel yestarday it seems that it behave better now but still have traffic starvation. I was on the devik page, but cant understand which patch is applied and which not..!?hope that 2.4.22 is the last..cant make many experiments cause it is working server. Nothing suspicious in the logs. Does someone have a setup with hundered of channels ! I spotted the problem ''cause a...

...cot listens the entire time. >> >> If the socket were closed during regeneration, then a (basic) front-end >> load balancer wouldn't still push connections to that proxy during regen. >> >> Rick > > I wonder if what is taking 5 minutes is CPU usage or entropy starvation. > Might be worth looking into. I'd say CPU usage - I have two identical VMs for dovecot proxies, one is hosted on a dual Xeon 5450, the other a dual Opteron 2347HE.? Both hosts are under similar load, but the Xeon host was done within 30 seconds. I assume the Xeon, besides having a faster...

...ailable per-socket is 256 KB, but if we use >>> only 1 byte per packet, the guest can queue up to 262144 of 4 KB >>> buffers, using up to 1 GB of memory per-socket. In addition, the >>> guest will continue to fill the vring with new 4 KB free buffers >>> to avoid starvation of her sockets. >>> >>> This patch solves this issue copying the payload in a new buffer. >>> Then it is queued in the per-socket list, and the 4KB buffer used >>> by the host is freed. >>> >>> In this way, the memory used by each socket respect...

...ailable per-socket is 256 KB, but if we use >>> only 1 byte per packet, the guest can queue up to 262144 of 4 KB >>> buffers, using up to 1 GB of memory per-socket. In addition, the >>> guest will continue to fill the vring with new 4 KB free buffers >>> to avoid starvation of her sockets. >>> >>> This patch solves this issue copying the payload in a new buffer. >>> Then it is queued in the per-socket list, and the 4KB buffer used >>> by the host is freed. >>> >>> In this way, the memory used by each socket respect...