summaryrefslogtreecommitdiffstats
path: root/src/svm
AgeCommit message (Expand)AuthorFilesLines
2017-09-01Add fixed-size, preallocated pool supportDave Barach1-1/+1
2017-08-29session: segment manager improvementsFlorin Coras3-25/+60
2017-08-25tcp: retransmit and multi-buffer segment fixes and improvementsFlorin Coras1-7/+7
2017-08-25jvpp: introducing callback api and future api tests for all plugins (VPP-591)Matej Perina1-1/+1
2017-08-18API: More gracefully fail when opening shared memory segment fails.Ole Troan2-6/+9
2017-08-14jvpp: make shm_prefix configurable (VPP-591)Jan Srnicek1-1/+2
2017-08-10Improve the svm fifo allocatorDave Barach4-17/+127
2017-08-10TCP proxy prototypeDave Barach3-2/+14
2017-07-31ssvm->name must be a vector containing a c-string.Dave Wallace2-3/+5
2017-07-30Make tcp active open data structures thread safeFlorin Coras1-0/+6
2017-07-17Fix unlinking of /dev/shm files.Dave Wallace4-14/+52
2017-07-15Fixes and improved tcp/session debuggingFlorin Coras2-40/+151
2017-07-11Horizontal (nSessions) scaling draftDave Barach6-59/+158
2017-07-01Refactor API message handling codeKlement Sekera2-101/+134
2017-06-22Improve svm fifo and tcp tx path performance (VPP-846)Florin Coras1-5/+90
2017-06-19Overall tcp performance improvements (VPP-846)Florin Coras3-75/+110
2017-06-09Implement sack based tcp loss recovery (RFC 6675)Florin Coras1-2/+3
2017-06-01Improve fifo allocator performanceDave Barach4-36/+168
2017-05-20Improve session debuggingFlorin Coras1-4/+5
2017-05-17VPP-846: tcp perf / scale / hardeningDave Barach1-2/+2
2017-05-09Fix remaining 32-bit compile issuesDamjan Marion2-7/+8
2017-05-03A sprinkling of const in vlibmemory/api.h and friendsNeale Ranns3-9/+9
2017-05-01TCP ooo reception fixesFlorin Coras2-75/+70
2017-04-24Session layer improvementsFlorin Coras5-61/+82
2017-04-19Add more svm fifo unit testsFlorin Coras1-54/+46
2017-04-18Fix fifo ooo bugs and improve testingDave Barach2-38/+109
2017-04-13Session layer refactoringFlorin Coras3-52/+60
2017-04-02TCP cc/window management fixes and debuggingFlorin Coras2-19/+26
2017-03-27TCP/session improvementsFlorin Coras3-20/+47
2017-03-04Cleanup URI code and TCP bugfixingFlorin Coras1-3/+3
2017-03-01VPP-598: tcp stack initial commitDave Barach7-7/+1395
2016-12-28Reorganize source tree to use single autotools instanceDamjan Marion11-0/+4006
t modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.