- 30 Aug, 2018 1 commit
-
-
Poul-Henning Kamp authored
-
- 29 Aug, 2018 3 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
... and fail the VCL unless successful. Providing the PRIVs to vmods is a core function, so error handling should happen outside vmods. Besides being safe, this initialization can be more efficient than previous code for PRIVs used frequently within the same subroutine. An alternative approach would be to initialize all privs once per task / top request, but unless all privs are actually used in a VCL, this approach could impose significant overhead, both in terms of time and memory. By initializing privs once per sub, we impose overhead for privs which are referenced but not actually used in a subroutine, but not for all of the vcl. Fixes #2708
-
Poul-Henning Kamp authored
-
- 28 Aug, 2018 10 commits
-
-
Poul-Henning Kamp authored
per-task PRIVs. Fixes: #2749
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
the purpose of VRT_priv_task()
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Poul-Henning Kamp authored
Previously we used various heuristics (test TCP connection) to avoid the reschedule if the req was abandonned while on the waiting list. We also subjected the rescheduling to pool-queue limits like any new request. This was all safe because we knew we could clean up the request state cheaply, even if it was somewhat cumbersome. Now vmods can have per-task PRIV's and we have no idea what it will cost us (stack, time, etc) to clean them up, so we cannot burden J.Random Request who happens to rush the waiting list with the burden. Fix this by always rescheduling, not subject to pool-queue limits, and eliminate all the special-casing for exceeded limits, including the debug feature to force a rescheduling failure and two tests exercising it. As a side effect of this, requests on the waiting list gets a "business class upgrade" over newly arriving requests when there are no worker threads available. Given that these requests arrived earlier, and we already performed work on them, this seems only fair. Forced to pay proper attention by: slink
-
Nils Goroll authored
works around #2297
-
Nils Goroll authored
-
Dridi Boukelmoune authored
-
Poul-Henning Kamp authored
-
- 27 Aug, 2018 5 commits
-
-
Dridi Boukelmoune authored
-
Nils Goroll authored
-
Nils Goroll authored
Fixes #2746
-
Denes Matetelki authored
Increasing libvarnishapi.so version from 1.0.6 to 2.0.0
-
Dridi Boukelmoune authored
-
- 25 Aug, 2018 1 commit
-
-
Dridi Boukelmoune authored
-
- 24 Aug, 2018 1 commit
-
-
Poul-Henning Kamp authored
Submitted by: Frederic Lecaille <flecaille@haproxy.com>
-
- 23 Aug, 2018 3 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 22 Aug, 2018 16 commits
-
-
Guillaume Quintard authored
-
Guillaume Quintard authored
-
guillaume quintard authored
-
Guillaume Quintard authored
-
Federico G. Schwindt authored
-
Nils Goroll authored
Ref: c2888919 72bacde7 46f1557d
-
Nils Goroll authored
-
Poul-Henning Kamp authored
In other news: VTEST works.
-
Poul-Henning Kamp authored
Fixes: #2696
-
Nils Goroll authored
* either NULL or properly named * only named arguments can be possibly be speficied multiple times * only named arguments can be optional * positional arguments could be missing
-
Poul-Henning Kamp authored
Fixes #2694
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-