All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Herbert <tom@herbertland.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: <kernel-team@fb.com>, <davejwatson@fb.com>
Subject: [PATCH net-next 0/3] strp: Generalize stream parser to work with other socket types
Date: Sun, 28 Aug 2016 14:43:16 -0700	[thread overview]
Message-ID: <1472420599-510735-1-git-send-email-tom@herbertland.com> (raw)

Add a read_sock protocol operation function that allows something like
tcp_read_sock to be called for other protocol types.

Specific changes in this patch set:
  - Add read_sock function to proto_ops. This has the same signature as
    tcp_read_sock. sk_read_actor_t is also defined in net.h.
  - Set peek_len and read_sock proto_op functions for TCPv4 and TCPv6
    stream ops.
  - Remove references to tcp in strparser.
  - Call peek_len and read_sock operations from strparser instead of
    calling TCP specific functions.

Tom Herbert (3):
  net: Add read_sock proto_op
  tcp: Set read_sock and peek_len proto_ops
  kcm: Remove TCP specific references from kcm and strparser

 include/linux/net.h       |  6 ++++++
 include/net/strparser.h   |  2 +-
 include/net/tcp.h         |  4 ++--
 net/ipv4/af_inet.c        |  2 ++
 net/ipv4/tcp.c            |  6 ++++++
 net/ipv6/af_inet6.c       |  2 ++
 net/kcm/kcmsock.c         | 30 +++++++++++++----------------
 net/strparser/strparser.c | 48 ++++++++++++++++++++++++++++-------------------
 8 files changed, 61 insertions(+), 39 deletions(-)

-- 
2.8.0.rc2

             reply	other threads:[~2016-08-28 21:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28 21:43 Tom Herbert [this message]
2016-08-28 21:43 ` [PATCH net-next 1/3] net: Add read_sock proto_op Tom Herbert
2016-08-28 21:43 ` [PATCH net-next 2/3] tcp: Set read_sock and peek_len proto_ops Tom Herbert
2016-08-28 21:43 ` [PATCH net-next 3/3] kcm: Remove TCP specific references from kcm and strparser Tom Herbert
2016-08-29  3:34 ` [PATCH net-next 0/3] strp: Generalize stream parser to work with other socket types David Miller
2016-08-29 15:52   ` Tom Herbert

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=1472420599-510735-1-git-send-email-tom@herbertland.com \
    --to=tom@herbertland.com \
    --cc=davejwatson@fb.com \
    --cc=davem@davemloft.net \
    --cc=kernel-team@fb.com \
    --cc=netdev@vger.kernel.org \
    /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.