From Fedora Project Wiki
mNo edit summary
mNo edit summary
Line 11: Line 11:
== Summary ==
== Summary ==
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
Acceleration of GnuTLS with software Kernel TLS(KTLS)


== Owner ==
== Owner ==
Line 33: Line 34:


<!-- Select proper category, default is Self Contained Change -->
<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
<!-- [[Category:SelfContainedChange]] -->
<!-- [[Category:SystemWideChange]] -->
[[Category:SystemWideChange]]


* Targeted release: [[Releases/38 | Fedora Linux 38 ]]  
* Targeted release: [[Releases/38 | Fedora Linux 38 ]]  
Line 49: Line 50:


== Detailed Description ==
== Detailed Description ==
The goal of this change is to provide GnuTLS users with a high throughput data transfer mechanism on encrypted channels, with emphasis on network block devices(NBD).
The goal of this change is to provide GnuTLS users with a high throughput data transfer mechanism on encrypted channels, with emphasis on network block devices(NBD).


We accomplish this with KTLS which offloads enc/decryption to the kernel (possibly to NIC), while GnuTLS handles initial connection(TLS handshake). This approach saves us from frequent context switching as well as data copies in userspace when using send_file() function.
We accomplish this with KTLS which offloads enc/decryption to the kernel (possibly to NIC), while GnuTLS handles initial connection(TLS handshake). This approach saves us from frequent context switching as well as data copies in userspace when using send_file() function.
Line 84: Line 85:
     https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
     https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
-->
-->
== Scope ==
== Scope ==
* Proposal owners:
* Proposal owners:

Revision as of 12:57, 18 July 2022

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
Idea.png
Guidance
For details on how to fill out this form, see the documentation.


KTLS implementation for GnuTLS

Important.png
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

Acceleration of GnuTLS with software Kernel TLS(KTLS)

Owner


Current status

  • Targeted release: Fedora Linux 38
  • Last updated: 2022-07-18
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

The goal of this change is to provide GnuTLS users with a high throughput data transfer mechanism on encrypted channels, with emphasis on network block devices(NBD).

We accomplish this with KTLS which offloads enc/decryption to the kernel (possibly to NIC), while GnuTLS handles initial connection(TLS handshake). This approach saves us from frequent context switching as well as data copies in userspace when using send_file() function.

Feedback

Benefit to Fedora

Scope

  • Proposal owners:
  • Other developers:
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

How To Test

User Experience

Dependencies

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No


Documentation

N/A (not a System Wide Change)

Release Notes