diff options
| author | David S. Miller <davem@davemloft.net> | 2019-06-11 21:22:27 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2019-06-11 21:22:27 +0200 |
| commit | 758a0a4d60ab8a5bfed1e8365c6faa00d8b8dbd5 (patch) | |
| tree | 540add3d2e40be7263d64cde02b30a0ca8dd7cbe /net/sched/sch_ingress.c | |
| parent | packet: remove unused variable 'status' in __packet_lookup_frame_in_block (diff) | |
| parent | nfp: tls: make use of kernel-driven TX resync (diff) | |
| download | linux-758a0a4d60ab8a5bfed1e8365c6faa00d8b8dbd5.tar.xz linux-758a0a4d60ab8a5bfed1e8365c6faa00d8b8dbd5.zip | |
Merge branch 'tls-add-support-for-kernel-driven-resync-and-nfp-RX-offload'
Jakub Kicinski says:
====================
tls: add support for kernel-driven resync and nfp RX offload
This series adds TLS RX offload for NFP and completes the offload
by providing resync strategies. When TLS data stream looses segments
or experiences reorder NIC can no longer perform in line offload.
Resyncs provide information about placement of records in the
stream so that offload can resume.
Existing TLS resync mechanisms are not a great fit for the NFP.
In particular the TX resync is hard to implement for packet-centric
NICs. This patchset adds an ability to perform TX resync in a way
similar to the way initial sync is done - by calling down to the
driver when new record is created after driver indicated sync had
been lost.
Similarly on the RX side, we try to wait for a gap in the stream
and send record information for the next record. This works very
well for RPC workloads which are the primary focus at this time.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/sched/sch_ingress.c')
0 files changed, 0 insertions, 0 deletions