All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
	alexei.starovoitov@gmail.com, davejwatson@fb.com,
	john.fastabend@gmail.com, vakul.garg@nxp.com,
	borisp@mellanox.com,
	Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: [PATCH net 0/3] Documentation: tls: add offload documentation
Date: Wed, 15 May 2019 13:41:20 -0700	[thread overview]
Message-ID: <20190515204123.5955-1-jakub.kicinski@netronome.com> (raw)

Hi!

This set adds documentation for TLS offload. It starts
by making the networking documentation a little easier
to navigate by hiding driver docs a little deeper.
It then RSTifys the existing Kernel TLS documentation.
Last but not least TLS offload documentation is added.
This should help vendors navigate the TLS offload, and
help ensure different implementations stay aligned from
user perspective.

---
Dave, this just documents existing code, so I ventured
to post during the merge window, not 100% sure it is
appropriate at this stage..

Jakub Kicinski (3):
  Documentation: net: move device drivers docs to a submenu
  Documentation: tls: RSTify the ktls documentation
  Documentation: add TLS offload documentation

 .../networking/device_drivers/index.rst       |  30 ++
 Documentation/networking/index.rst            |  16 +-
 .../networking/tls-offload-layers.svg         |   1 +
 .../networking/tls-offload-reorder-bad.svg    |   1 +
 .../networking/tls-offload-reorder-good.svg   |   1 +
 Documentation/networking/tls-offload.rst      | 438 ++++++++++++++++++
 Documentation/networking/{tls.txt => tls.rst} |  44 +-
 7 files changed, 505 insertions(+), 26 deletions(-)
 create mode 100644 Documentation/networking/device_drivers/index.rst
 create mode 100644 Documentation/networking/tls-offload-layers.svg
 create mode 100644 Documentation/networking/tls-offload-reorder-bad.svg
 create mode 100644 Documentation/networking/tls-offload-reorder-good.svg
 create mode 100644 Documentation/networking/tls-offload.rst
 rename Documentation/networking/{tls.txt => tls.rst} (88%)

-- 
2.21.0


             reply	other threads:[~2019-05-15 20:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15 20:41 Jakub Kicinski [this message]
2019-05-15 20:41 ` [PATCH net 1/3] Documentation: net: move device drivers docs to a submenu Jakub Kicinski
2019-05-15 20:41 ` [PATCH net 2/3] Documentation: tls: RSTify the ktls documentation Jakub Kicinski
2019-05-15 20:41 ` [PATCH net 3/3] Documentation: add TLS offload documentation Jakub Kicinski
2019-05-16  9:08   ` Boris Pismenny
2019-05-16 17:56     ` Jakub Kicinski
2019-05-16 18:13       ` Alexei Starovoitov
2019-05-16 18:42         ` Jakub Kicinski
2019-05-16 19:32           ` Alexei Starovoitov
2019-05-16 21:39             ` Jakub Kicinski
2019-05-16 22:52               ` Alexei Starovoitov
2019-05-17  0:13                 ` Jakub Kicinski
2019-05-19  6:24       ` Boris Pismenny
2019-05-20 19:02         ` Jakub Kicinski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190515204123.5955-1-jakub.kicinski@netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=borisp@mellanox.com \
    --cc=davejwatson@fb.com \
    --cc=davem@davemloft.net \
    --cc=john.fastabend@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.com \
    --cc=vakul.garg@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.