From: Marcelo Ricardo Leitner <marcelo.leitner@gmail•com>
To: netdev@vger•kernel.org
Cc: Neil Horman <nhorman@tuxdriver•com>,
Vlad Yasevich <vyasevich@gmail•com>,
linux-sctp@vger•kernel.org
Subject: [PATCH 0/2] sctp: delay calls to sk_data_ready() as much as possible
Date: Tue, 29 Mar 2016 10:49:43 -0300 [thread overview]
Message-ID: <cover.1459259208.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.
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 | 5 +++++
net/sctp/ulpqueue.c | 4 ++--
3 files changed, 14 insertions(+), 8 deletions(-)
--
2.5.0
next reply other threads:[~2016-03-29 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 13:49 Marcelo Ricardo Leitner [this message]
2016-03-29 13:49 ` [PATCH 1/2] sctp: compress bit-wide flags to a bitfield on sctp_sock Marcelo Ricardo Leitner
2016-03-29 13:49 ` [PATCH 2/2] sctp: delay calls to sk_data_ready() as much as possible Marcelo Ricardo 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.1459259208.git.marcelo.leitner@gmail.com \
--to=marcelo.leitner@gmail$(echo .)com \
--cc=linux-sctp@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nhorman@tuxdriver$(echo .)com \
--cc=vyasevich@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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