#
18b4fd62 |
| 10-Nov-2015 |
Randall Stewart <rrs@FreeBSD.org> |
Add new async_drain to the callout system. This is so-far not used but should be used by TCP for sure in its cleanup of the IN-PCB (will be coming shortly).
Sponsored by: Netflix Inc. Differential R
Add new async_drain to the callout system. This is so-far not used but should be used by TCP for sure in its cleanup of the IN-PCB (will be coming shortly).
Sponsored by: Netflix Inc. Differential Revision: https://reviews.freebsd.org/D4076
show more ...
|
#
11d38a57 |
| 28-Oct-2015 |
Baptiste Daroussin <bapt@FreeBSD.org> |
Merge from head
Sponsored by: Gandi.net
|
#
becbad1f |
| 13-Oct-2015 |
Baptiste Daroussin <bapt@FreeBSD.org> |
Merge from head
|
#
65dcb5bc |
| 01-Oct-2015 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r288197 through r288456.
|
#
5a2b666c |
| 01-Oct-2015 |
Baptiste Daroussin <bapt@FreeBSD.org> |
Merge from head
|
#
0f405ee7 |
| 28-Sep-2015 |
Navdeep Parhar <np@FreeBSD.org> |
Sync up with head (up to r288341).
|
#
2f2f522b |
| 28-Sep-2015 |
Andriy Gapon <avg@FreeBSD.org> |
save some bytes by using more concise SDT_PROBE<n> instead of SDT_PROBE
SDT_PROBE requires 5 parameters whereas SDT_PROBE<n> requires n parameters where n is typically smaller than 5.
Perhaps SDT_P
save some bytes by using more concise SDT_PROBE<n> instead of SDT_PROBE
SDT_PROBE requires 5 parameters whereas SDT_PROBE<n> requires n parameters where n is typically smaller than 5.
Perhaps SDT_PROBE should be made a private implementation detail.
MFC after: 20 days
show more ...
|
#
26e065d0 |
| 22-Sep-2015 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r288035 through r288099.
|
#
c55f4c94 |
| 22-Sep-2015 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Revert r287780 until more developers have their say.
Differential Revision: https://reviews.freebsd.org/D3521 Requested by: gnn
|
#
a1cb6af1 |
| 17-Sep-2015 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r287680 through r287877.
|
#
9acc0eaf |
| 14-Sep-2015 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Implement callout_drain_async(), inspired by the projects/hps_head branch.
This function is used to drain a callout via a callback instead of blocking the caller until the drain is complete. Refer t
Implement callout_drain_async(), inspired by the projects/hps_head branch.
This function is used to drain a callout via a callback instead of blocking the caller until the drain is complete. Refer to the callout_drain_async() manual page for a detailed description.
Limitation: If a lock is used with the callout, the callout can only be drained asynchronously one time unless the callout_init_mtx() function is called again. This limitation is not present in projects/hps_head and will require more invasive changes to the timeout code, which was not in the scope of this patch.
Differential Revision: https://reviews.freebsd.org/D3521 Reviewed by: wblock MFC after: 1 month
show more ...
|
#
f94594b3 |
| 12-Sep-2015 |
Baptiste Daroussin <bapt@FreeBSD.org> |
Finish merging from head, messed up in previous attempt
|
#
00176600 |
| 09-Sep-2015 |
Navdeep Parhar <np@FreeBSD.org> |
Merge r286744-r287584 from head.
|
#
d9442b10 |
| 05-Sep-2015 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r286858 through r287489.
|
#
378d5c6c |
| 01-Sep-2015 |
Andriy Gapon <avg@FreeBSD.org> |
callout_reset: fix a reversed check for cc_exec_cancel
The typo was introduced in r278469 / 344ecf88af2dfb.
As a result of the bug there was a timing window where callout_reset() would fail to canc
callout_reset: fix a reversed check for cc_exec_cancel
The typo was introduced in r278469 / 344ecf88af2dfb.
As a result of the bug there was a timing window where callout_reset() would fail to cancel a concurrent execution of a callout that is about to start and would schedule the callout again. The callout would fire more times than it is scheduled. That would happen even if the callout is initialized with a lock.
For example, the bug triggered the "Stray timeout" assertion in taskqueue_timeout_func().
MFC after: 5 days
show more ...
|
#
2ea3089c |
| 30-Aug-2015 |
Julien Charbon <jch@FreeBSD.org> |
Revert r286880: If at first this change made sense, it turns out it helps only the TCP timers callout(9) usage. As the benefit for others callout(9) usages did not reach a consensus the historical
Revert r286880: If at first this change made sense, it turns out it helps only the TCP timers callout(9) usage. As the benefit for others callout(9) usages did not reach a consensus the historical usage should prevail.
Differential Revision: https://reviews.freebsd.org/D3078
show more ...
|
#
cd252ea7 |
| 27-Aug-2015 |
Julien Charbon <jch@FreeBSD.org> |
Silent a compilation warning on callout_stop()
|
#
682d0e15 |
| 27-Aug-2015 |
Julien Charbon <jch@FreeBSD.org> |
In callout_stop(), do not forget to initialize not_running variable. Thanks to hselasky for noticing that.
Differential Revision: https://reviews.freebsd.org/D3078 (Updated) Submitted by: hselasky
In callout_stop(), do not forget to initialize not_running variable. Thanks to hselasky for noticing that.
Differential Revision: https://reviews.freebsd.org/D3078 (Updated) Submitted by: hselasky Pointy hat to: jch
show more ...
|
#
0cfae4b4 |
| 27-Aug-2015 |
Julien Charbon <jch@FreeBSD.org> |
In callout_stop(), if a callout is both pending and currently being serviced return 0 (fail) but it is applicable only mpsafe callouts. Thanks to hselasky for finding this.
Differential Revision: h
In callout_stop(), if a callout is both pending and currently being serviced return 0 (fail) but it is applicable only mpsafe callouts. Thanks to hselasky for finding this.
Differential Revision: https://reviews.freebsd.org/D3078 (Updated) Submitted by: hselasky Reviewed by: jch
show more ...
|
#
23a32822 |
| 25-Aug-2015 |
Baptiste Daroussin <bapt@FreeBSD.org> |
Merge from HEAD
|
#
a1e6f8ff |
| 18-Aug-2015 |
Julien Charbon <jch@FreeBSD.org> |
callout_stop() should return 0 (fail) when the callout is currently being serviced and indeed unstoppable.
A scenario to reproduce this case is:
- the callout is being serviced and at same time, -
callout_stop() should return 0 (fail) when the callout is currently being serviced and indeed unstoppable.
A scenario to reproduce this case is:
- the callout is being serviced and at same time, - callout_reset() is called on this callout that sets the CALLOUT_PENDING flag and at same time, - callout_stop() is called on this callout and returns 1 (success) even if the callout is indeed currently running and unstoppable.
This issue was caught up while making r284245 (D2763) workaround, and was discussed at BSDCan 2015. Once applied the r284245 workaround is not needed anymore and will be reverted.
Differential Revision: https://reviews.freebsd.org/D3078 Reviewed by: jhb Sponsored by: Verisign, Inc.
show more ...
|
Revision tags: release/10.2.0 |
|
#
416ba5c7 |
| 22-Jun-2015 |
Navdeep Parhar <np@FreeBSD.org> |
Catch up with HEAD (r280229-r284686).
|
#
98e0ffae |
| 27-May-2015 |
Simon J. Gerraty <sjg@FreeBSD.org> |
Merge sync of head
|
#
7757a1b4 |
| 03-May-2015 |
Baptiste Daroussin <bapt@FreeBSD.org> |
Merge from head
|
#
7263c8c0 |
| 22-Apr-2015 |
Glen Barber <gjb@FreeBSD.org> |
MFH: r280643-r281852
Sponsored by: The FreeBSD Foundation
|