From: Rao Shoaib <Rao.Shoaib@oracle.com>
To: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
rao.shoaib@oracle.com, viro@zeniv.linux.org.uk,
pabeni@redhat.com
Subject: [PATCH net-next af_unix v1 0/1] af_unix: Add OOB support
Date: Sun, 1 Aug 2021 00:57:06 -0700 [thread overview]
Message-ID: <20210801075707.176201-1-Rao.Shoaib@oracle.com> (raw)
From: Rao Shoaib <rao.shoaib@oracle.com>
The original Berkeley paper on sockets by Bill Joy
http://maibriz.de/unix/ultrix/_root/net.pdf
defined OOB support for all streams sockets.
However, this support was never added to AF_UNIX
streams sockets, probably because it was not needed.
With several containers running on the same host, AF_UNIX sockets
are being used instead of TCP sockets because they are efficient.
Papers have been published that show the performance benefit of using
AF_UNIX sockets and mention lack of OOB support.
https://www.usenix.org/system/files/conference/atc15/atc15-paper-dietz.pdf
Products are also being built that require OOB support for AF_UNIX sockets.
This patch adds OOB support to AF_UNIX stream sockets. The semantics
are same as that of TCP.
Rao Shoaib (1):
af_unix: Add OOB support
include/net/af_unix.h | 3 +
net/unix/Kconfig | 5 +
net/unix/af_unix.c | 153 +++++-
tools/testing/selftests/Makefile | 1 +
tools/testing/selftests/net/af_unix/Makefile | 5 +
.../selftests/net/af_unix/test_unix_oob.c | 437 ++++++++++++++++++
6 files changed, 602 insertions(+), 2 deletions(-)
create mode 100644 tools/testing/selftests/net/af_unix/Makefile
create mode 100644 tools/testing/selftests/net/af_unix/test_unix_oob.c
--
2.31.1
next reply other threads:[~2021-08-01 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 7:57 Rao Shoaib [this message]
2021-08-01 7:57 ` [PATCH net-next af_unix v1 1/1] af_unix: Add OOB support Rao Shoaib
2021-08-04 9:00 ` [PATCH net-next af_unix v1 0/1] " patchwork-bot+netdevbpf
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=20210801075707.176201-1-Rao.Shoaib@oracle.com \
--to=rao.shoaib@oracle.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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).