search for: worker_list

...} 587 goto found; 588 589 fallback: 590 fallback = NULL; 591 /* 592 * we have failed to find any workers, just 593 * return the first one we can find. 594 */ 595 if (!list_empty(&workers->worker_list)) 596 fallback = workers->worker_list.next; 597 if (!list_empty(&workers->idle_list)) 598 fallback = workers->idle_list.next; 599 BUG_ON(!fallback); 600 worker = list_entry(fallback, 601 s...

...o set up a test and see exactly how mod_proxy_balancer handles this... but... If I understand the problem correctly, then one solution might be moving lines 721 thru 734 into a loop, possibly in its own method, which does sth like this: def myaccept while true return @socket.accept if worker_list.length < num_processors ## check first to see if we can handle the request. Let client worry about connect timeouts. while @num_processors < reap_dead_workers sleep @loop_throttle end end end 720 @acceptor = Thread.new do 721 while true 7...

...trfs/async-thread.c @@ -424,11 +424,11 @@ int btrfs_requeue_work(struct btrfs_work *work) * list */ if (worker->idle) { - spin_lock_irqsave(&worker->workers->lock, flags); + spin_lock(&worker->workers->lock); worker->idle = 0; list_move_tail(&worker->worker_list, &worker->workers->worker_list); - spin_unlock_irqrestore(&worker->workers->lock, flags); + spin_unlock(&worker->workers->lock); } if (!worker->working) { wake = 1; -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs&quo...

..._opts @acceptor = Thread.new do while true begin client = @socket.accept - client.setsockopt(Socket::SOL_TCP, $tcp_cork_opts[0], $tcp_cork_opts[1]) if $tcp_cork_opts + client.setsockopt(*$tcp_cork_opts) if $tcp_cork_opts worker_list = @workers.list

...ml and not to mongrel, but I think maybe some of you hit this problem and solved it somehow. Another issue: on my system, mongrel_rails --version Mongrel Web Server 1.1.3 (installed as a gem) the --num-procs parameter does not seem to work. To debug the problem I added STDERR.puts "TEST: #{worker_list.length} #{@num_processors}" on line 279 of /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb, and to my surprise it looks like the parameter is ignored. If I run it $ mongrel_rails start -a 127.0.0.1 -p 8999 --num-procs 1 & [1] 18617 ** Starting Mongrel listening at 127.0.0.1:899...