From: David Laight <David.Laight@ACULAB.COM>
To: 'Matthew Wilcox' <willy@infradead.org>, Jakub Kicinski <kuba@kernel.org>
Cc: Shoaib Rao <rao.shoaib@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"andy.rudoff@intel.com" <andy.rudoff@intel.com>
Subject: RE: [PATCH] af_unix: Allow Unix sockets to raise SIGURG
Date: Fri, 29 Jan 2021 23:47:14 +0000 [thread overview]
Message-ID: <ee13e83b22b7411c97a2a961015343d1@AcuMS.aculab.com> (raw)
In-Reply-To: <20210129213217.GD308988@casper.infradead.org>
> I'd encourage anyone thinking about "using OOB" to read
> https://tools.ietf.org/html/rfc6093 first. Basically, TCP does not
> actually provide an OOB mechanism, and frankly Unix sockets shouldn't
> try either.
OOB data maps much better onto ISO transport 'expedited data'
than anything in a bytestream protocol like TCP.
There you can send a message (it is message oriented) that isn't
subject to normal data flow control.
The length is limited (IIRC 32 bytes) and expedited data has
its own credit of one, but can overtake (and is expected to
overtake) flow control blocked normal data.
All TCP provides is a byte sequence number for OOB data.
This is just a marker in the bytestream.
It really doesn't map onto the socket OOB data data all.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2021-01-29 23:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 15:06 [PATCH] af_unix: Allow Unix sockets to raise SIGURG Matthew Wilcox (Oracle)
2021-01-25 23:36 ` Jakub Kicinski
2021-01-29 17:56 ` Shoaib Rao
2021-01-29 19:06 ` Jakub Kicinski
2021-01-29 19:48 ` Shoaib Rao
2021-01-29 20:02 ` Jakub Kicinski
2021-01-29 20:10 ` Shoaib Rao
2021-01-29 20:18 ` Jakub Kicinski
2021-01-29 20:44 ` Shoaib Rao
2021-01-29 20:49 ` Shoaib Rao
2021-01-29 21:18 ` Jakub Kicinski
2021-01-29 21:32 ` Matthew Wilcox
2021-01-29 23:47 ` David Laight [this message]
2021-01-29 21:54 ` Shoaib Rao
2021-01-29 19:19 ` Matthew Wilcox
2021-01-29 19:54 ` Shoaib Rao
2021-01-29 20:01 ` Shoaib Rao
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=ee13e83b22b7411c97a2a961015343d1@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=andy.rudoff@intel.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rao.shoaib@oracle.com \
--cc=willy@infradead.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 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).