| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
1) Add four new points that allow you to get more information
to cc algo's
2) Fix the case where user changes module on a existing TCB, in
such a case, the initialization module needs to be called on all nets.
3) Move htcp_cc structure to a union that other modules can use.
4) Add 5th point for get/set socket options for cc_module specific options
MFC after: 2 months
|
|
|
|
|
|
| |
* Fix an initialization bug for the scaled variance of the RTO.
MFC after: 3 months.
|
|
|
|
|
| |
2) Mass update to all copyrights.
MFC after: 3 Months
|
|
|
|
|
|
| |
From Robin Seggelmann.
MFC after: 3 months.
|
|
|
|
|
|
| |
exisiting associations and endpoints.
MFC after: 3 months.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2) Add separate max-bursts for retransmit and hb. These
are set to sysctlable values but not settable via the
socket api. This makes sure we don't blast out HB's or
fast-retransmits.
3) Determine on the first data transmission on a net if
its local-lan (by being under or over a RTT). This
can later be used to think about different algorithms
based on locallan vs big-i (experimental)
4) The cwnd should NOT be allowed to grow when an ECNEcho
is seen (TCP has this same bug). We fix this in SCTP
so an ECNe being seen prevents an advance of cwnd.
5) CWR's should not be sent multiple times to the
same network, instead just updating the TSN being
transmitted if needed.
MFC after: 1 Month
|
|
|
|
|
|
|
|
|
|
|
| |
1) We now remove ECN-Nonce since it will no longer continue as a I-D
2) Eliminate last_tsn_echo, this tied us to an assoc not the net
and thus we were not doing m-homing on the ECN-Echo senders side right.
3) Increment the count going out even if the TSN in lower in the pending
ECN-Echo, this way the receiver knows exactly how many packets were
marked even with network re-ordering
4) Fix so we DO NOT stop doing delayed sack if a ECN Echo is in queue
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) ECN was on an association basis, this is incorrect and
will not work with CMT or for that matter if the user
is sending to multiple addresses. This commit makes
ECN on a per path basis.
2) Adopt the new format for the ECN internet draft. This also
maintains compatability with old format chunks as well.
3) Keep track of the real time of a RTT down to micro seconds.
For some future conditional features (for like a data center
this is good information to have).
MFC after: 1 month
|
|
|
|
|
|
|
|
|
| |
This will be used for Data Center congestion
control, we won't want to engage it in the
ECN code unless we KNOW that the RTT is less
than 500us.
MFC after: 1 week
|
|
|
|
|
|
| |
This work is based on a patch received from Robin Seggelmann.
MFC after: 3 months.
|
|
|
|
| |
MFC after: 3 months.
|
|
|
|
| |
MFC after: 3 months.
|
|
|
|
|
|
|
| |
TAILQ_FOREACH_SAFE where appropriate.
No functional change.
MFC after: 3 months.
|
|
|
|
|
|
| |
association is aborted via sctp_abort_association().
MFC after: 3 days.
|
|
|
|
| |
MFC after: 3 days.
|
|
|
|
|
|
| |
1-to-1 style sockets when an ABORT was received.
MFC after: 3 days.
|
|
|
|
|
|
|
|
| |
function from the timer code to util, rename it appropriately and
also fix a bug in sctp_get_prev_mtu(), where calling it with a
value existing in the MTU table did not return a smaller one.
MFC after: 3 days.
|
|
|
|
|
|
| |
but also when entering the SHUTDOWN_ACK_SEND state.
MFC after: 3 days.
|
|
|
|
| |
MFC after: 2 weeks.
|
|
|
|
| |
MFC after: 3 weeks.
|
|
|
|
|
|
|
| |
the sent_queue. Honor a given path when the SCTP_ADDR_OVER
flag is set.
MFC after: 2 weeks.
|
|
|
|
|
|
| |
due to the fact that its bogus.. nam->sa_family will
not change from AF_INET6 to AF_INET (but clang
thinks it does ;-D)
|
|
|
|
|
|
|
|
| |
Fix the switching on/off of PF and NR-SACKs using sysctl.
Add minor improvement in handling malloc failures.
Improve the address checks when sending.
MFC after: 4 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
large number of packets queued to a crashing process.
In a specific case you may get 2 ABORT's back (from
say two packets in flight). If the aborts happened to
be processed at the same time its possible to have
one free the association while the other is trying
to report all the outbound packets. When this occured
it could lead to a crash.
MFC after: 3 days
|
|
|
|
|
|
| |
The race condition resulted in a panic.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a) There was a case where a ICMP message could cause
us to return leaving a stuck lock on an stcb.
b) The iterator needed some tweaks to fix its lock
ordering.
c) The ITERATOR_LOCK is no longer needed in the freeing
of a stcb. Now that the timer based one is gone we don't
have a multiple resume situation. Add to that that there
was somewhere a path out of the freeing of an assoc that
did NOT release the iterator_lock.. it was time to clean
this old code up and in the process fix the lock bug.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of apitesters.. Basically we end up with attempting
to destroy a lock thats contended on. A cookie echo
arrives at the same time that the close is happening.
The close gets the lock but the cookie echo has already
passed the check for the gone flag and is then locked
waiting on the create lock.. when we go to destroy it
bam. For now we do the timer destroy for all calls
to close.. We can probably optimize this later so that
we check whats being contended on and if there is contention
then do the timer thing. but this is probably safest since
the inp has been removed from all lists and references and
only the timer can find it.. once the locks are released all
other places will instantly see the GONE flag and bail (thats
what the change in sctp_input is one place that was lacking
the bail code).
MFC after: 1 week
|
|
|
|
|
|
|
| |
when the gone flag is set. You don't know what locks the
caller has set and there is already a kill timer running.
MFC after: 1 week
|
|
|
|
|
|
| |
past the scrubber.
MFC after: 1 Week
|
|
|
|
|
|
|
|
|
| |
code base. We now properly have ONE thread
that services all VNET's. Also we purge out
the old timer based iterator code which had
multiple LOR's and other issues.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
* Fix delaying of SACK by taking out old optimization code
which does not optimize anymore.
* Fix fast retransmission of chunks abandoned by the
"number of retransmissions" policy.
MFC after: 3 days.
|
|
|
|
| |
MFC after: 3 days.
|
|
|
|
|
|
| |
Fix sctp_print_mapping_array().
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
* Fix handling of mapping arrays when draining mbufs or processing
FORWARD-TSN chunks.
* Cleanup code (no duplicate code anymore for SACKs and NR-SACKs).
Part of this code was developed together with rrs.
MFC after: 2 weeks.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
enabled. Basically most of the operations were incorrect causing
bad sacks when you enabled nr-sack. The fixes range across
4 files and unifiy most of the processing so that we only test
nr_sack flags to decide which type of sack to generate.
Optimization left for this is to combine the sack generation
code and make it capable of generating either sack thus shrinking
out a routine.
Reviewed by: tuexen@freebsd.org
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
mapping_array expansion would break. Basically
once we expanded the array we no longer had both
mapping arrays in sync which the sack processing code depends on.
This would mean we were randomly referring to memory that was probably
not there. This mostly just gave us bad sack results going back to the peer.
If INVARIENTS was on of course we would hit the panic routine in the sack_check
call.
We also add a print routine for the place where one would panic in
invarients so one can see what the main mapping array holds.
Reviewed by: tuexen@freebsd.org
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
* Remove an unused global variable.
* Fix an issue reported by Bruce Cran related to reusing SCTP socket which
where connected.
MFC after: 1 week
|
|
|
|
| |
made its way through the scrubber.
|
|
|
|
|
| |
Submitted by: Marc Balmer <marc@msys.ch>
MFC after: 1 week
|
|
|
|
|
|
| |
only copied around.
Approved by: rrs (mentor)
|
|
|
|
|
| |
Approved by: rrs (mentor)
MFC after: 1 month
|
|
|
|
|
|
| |
Contains code from bz.
Approved by: rrs (mentor)
MFC after: 1 month.
|
|
|
|
|
|
|
| |
which results in stalled associations.
Approved by: re, rrs (mentor)
MFC after: immediately
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
association setup.
* Fix a bug where message with illegal stream ids are not deleted.
* Fix a crash when reporting back unsent messages from the send_queue.
* Fix a bug related to INIT retransmission when the socket is already
closed.
* Fix a bug where associations were stalled when partial delivery API
was enabled.
* Fix a bug where the receive buffer size was smaller than the
partial_delivery_point.
Approved by: re, rrs (mentor)
MFC after: One day.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
processing code holds the read lock (when processing a
FWD-TSN for pr-sctp). If it finds stranded data that
can be given to the application, it calls sctp_add_to_readq().
The readq function also grabs this lock. So if INVAR is on
we get a double recurse on a non-recursive lock and panic.
This fix will change it so that readq() function gets a
flag to tell if the lock is held, if so then it does not
get the lock.
Approved by: re@freebsd.org (Kostik Belousov)
MFC after: 1 week
|
|
|
|
|
|
|
| |
returning early from sctp_add_to_readq().
Approved by: re, rrs (mentor)
MFC after: 2 weeks.
|
|
|
|
|
| |
was not being freed at term of association. Also get rid of
the MICHAELS_EXP code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- PR-SCTP had major issues when skipping through a multi-part message.
o Did not look at socket buffer.
o Did not properly handle the reassmebly queue.
o The MARKED segments could interfere and un-skip a chunk causing
a problem with the proper FWD-TSN.
o No FR of FWD-TSN's was being done.
- NR-Sack code was basically disabled. It needed fixes that
never got into the real code.
- CMT code had issues when the two paths were NOT the same b/w. We
found a few small bugs, but also the critcal one here was not
dividing the rwnd amongst the paths.
Obtained from: Michael Tuexen and myself at the IETF hack-fest ;-)
|
|
|
|
|
|
|
|
| |
- When sending large PR-SCTP messages over a
lossy link we would incorrectly calculate the fwd-tsn
- When receiving large multipart pr-sctp packets we would
incorrectly send back a SACK that would renege improperly
on already received packets thus causing unneeded retransmissions.
|
|
|
|
|
|
| |
testing..
MFC after: 1 month
|