From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: netdev@vger.kernel.org
Cc: Vlad Yasevich <vyasevich@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>,
linux-sctp@vger.kernel.org,
David Laight <David.Laight@ACULAB.COM>,
Jakub Sitnicki <jkbs@redhat.com>
Subject: [PATCH v3 0/2] sctp: delay calls to sk_data_ready() as much as possible
Date: Fri, 8 Apr 2016 16:41:26 -0300 [thread overview]
Message-ID: <cover.1460144373.git.marcelo.leitner@gmail.com> (raw)
1st patch is a preparation for the 2nd. The idea is to not call
->sk_data_ready() for every data chunk processed while processing
packets but only once before releasing the socket.
v2: patchset re-checked, small changelog fixes
v3: on patch 2, make use of local vars to make it more readable
Marcelo Ricardo Leitner (2):
sctp: compress bit-wide flags to a bitfield on sctp_sock
sctp: delay calls to sk_data_ready() as much as possible
include/net/sctp/structs.h | 13 +++++++------
net/sctp/sm_sideeffect.c | 7 +++++++
net/sctp/ulpqueue.c | 4 ++--
3 files changed, 16 insertions(+), 8 deletions(-)
--
2.5.0
next reply other threads:[~2016-04-08 19:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 19:41 Marcelo Ricardo Leitner [this message]
2016-04-08 19:41 ` [PATCH v3 1/2] sctp: compress bit-wide flags to a bitfield on sctp_sock Marcelo Ricardo Leitner
2016-04-12 19:50 ` Neil Horman
2016-04-08 19:41 ` [PATCH v3 2/2] sctp: delay calls to sk_data_ready() as much as possible Marcelo Ricardo Leitner
2016-04-14 3:05 ` [PATCH v3 0/2] " David Miller
2016-04-14 13:03 ` Neil Horman
2016-04-14 17:00 ` Marcelo Ricardo Leitner
2016-04-14 18:59 ` David Miller
2016-04-14 19:33 ` marcelo.leitner
2016-04-14 20:03 ` Neil Horman
2016-04-14 20:19 ` marcelo.leitner
2016-04-28 20:46 ` marcelo.leitner
2016-04-29 13:36 ` Neil Horman
2016-04-29 13:47 ` marcelo.leitner
2016-04-29 16:10 ` Neil Horman
2016-04-29 16:28 ` marcelo.leitner
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=cover.1460144373.git.marcelo.leitner@gmail.com \
--to=marcelo.leitner@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=jkbs@redhat.com \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).