From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Thomas Graf <tgraf@infradead.org>,
Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: Netlink limitations
Date: Tue, 09 Nov 2010 00:36:38 +0100 [thread overview]
Message-ID: <4CD88986.2000109@netfilter.org> (raw)
In-Reply-To: <alpine.LNX.2.01.1011081958410.31946@obet.zrqbmnf.qr>
On 08/11/10 20:21, Jan Engelhardt wrote:
> On Monday 2010-11-08 16:16, Thomas Graf wrote:
>>>
>>> Messages are not limited to 64k, individual attributes are. Holger
>>> started working on a nlattr32, which uses 32 bit for the length
>>> value.
>>
>> Also, it is not required to pack everything in attributes. Your protocol
>> may specify that the whole message payload consists of chained attributes.
>> Alternatively you may as well split your attribut chain and dump them
>> as several messages.
>
> Yeah with NETLINK_URELEASE that seems the way to go. However, what are
> compelling arguments to use Netlink over other forms of bidirectional
> communication? (To play devils advocate, one could use nlattr32/TLVs
> over ioctl too.)
Netlink also provides an event-based notification infrastructure. Of
course, you can implement that upon a new socket family that supports
your new ioctls operations taking things in TLV format.
However, I guess that the whole thing will start looking like netlink
quite a lot in the end ;-).
next prev parent reply other threads:[~2010-11-08 23:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-07 16:44 Netlink limitations Jan Engelhardt
2010-11-07 17:17 ` Patrick McHardy
2010-11-08 15:16 ` Thomas Graf
2010-11-08 19:21 ` Jan Engelhardt
2010-11-08 23:36 ` Pablo Neira Ayuso [this message]
2010-11-09 9:27 ` Patrick McHardy
2010-11-09 14:49 ` Thomas Graf
2010-11-09 20:20 ` Jan Engelhardt
2010-11-09 21:40 ` Thomas Graf
2010-11-09 22:02 ` Jan Engelhardt
2010-11-09 23:35 ` Thomas Graf
2010-11-09 23:42 ` Jan Engelhardt
2010-11-09 23:54 ` Thomas Graf
2010-11-09 11:58 ` Jan Engelhardt
2010-11-09 12:10 ` Jan Engelhardt
2010-11-09 12:24 ` Patrick McHardy
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=4CD88986.2000109@netfilter.org \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@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 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.