From: Patrick McHardy <kaber@trash.net>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: Harald Welte <laforge@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: ctnetlink questions
Date: Mon, 20 Oct 2003 20:43:02 +0200 [thread overview]
Message-ID: <3F942CB6.5060005@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0310201133040.23768-100000@filer.marasystems.com>
Henrik Nordstrom wrote:
>On Mon, 20 Oct 2003, Harald Welte wrote:
>
>
>>again, this seems a shortcoming of the netlink infrastructure. This
>>would be much better, if we'd actually have a reference to the socket of
>>the userspace process (since table dumps could be unicast anyway...).
>>
>>
>
>If it is a shortcoming of netlink or a shortcoming of how to reliably dump
>the content of a large hash buckets can be argued, but I tend to agree
>with you here.
>
>The dump operation should be connetion oriented with the userspace
>application, not purely datagram based. The kernel should know for certain
>if the userspace application terminates a dump operation mid-air.
>
Actually the kernel knows. If the socket is closed cb->done() is called.
However the kernel can not know if userspace still keeps the socket open
but doesn't read anymore. Connection oriented sockets don't help with this.
Best regards,
Patrick
next prev parent reply other threads:[~2003-10-20 18:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031019171851.GR21521@sunbeam.de.gnumonks.org>
2003-10-19 19:36 ` ctnetlink questions Patrick McHardy
2003-10-19 20:28 ` Harald Welte
2003-10-19 22:55 ` Patrick McHardy
2003-10-20 1:05 ` Henrik Nordstrom
2003-10-20 3:01 ` Patrick McHardy
2003-10-20 3:09 ` Patrick McHardy
2003-10-20 6:34 ` Henrik Nordstrom
2003-10-20 17:53 ` Patrick McHardy
2003-10-20 7:15 ` Harald Welte
2003-10-20 9:37 ` Henrik Nordstrom
2003-10-20 18:43 ` Patrick McHardy [this message]
2003-10-20 18:37 ` Harald Welte
2003-10-20 19:17 ` Patrick McHardy
2003-10-20 19:41 ` Balazs Scheidler
2003-10-20 20:20 ` Patrick McHardy
2003-10-20 22:59 ` Harald Welte
2003-10-20 18:17 ` Patrick McHardy
2003-10-20 18:39 ` Harald Welte
2003-10-20 19:21 ` Patrick McHardy
2003-10-21 16:47 ` Patrick McHardy
2003-10-21 19:54 ` Henrik Nordstrom
2003-10-21 20:00 ` Patrick McHardy
2003-10-20 18:52 ` Harald Welte
2003-10-20 19:52 ` Patrick McHardy
2003-10-20 23:09 ` Harald Welte
2003-10-20 7:04 ` Harald Welte
2003-10-20 7:17 ` Jozsef Kadlecsik
2003-10-20 9:29 ` Henrik Nordstrom
2004-02-06 18:52 ` Harald Welte
2004-02-09 10:33 ` Pablo Neira
2004-02-10 12:39 ` Patrick McHardy
2004-02-14 20:03 ` Harald Welte
2004-02-15 10:01 ` Patrick McHardy
2004-02-17 21:37 ` Harald Welte
2003-10-20 14:48 ` Harald Welte
2003-10-20 18:53 ` Patrick McHardy
2003-10-20 22:57 ` Harald Welte
2003-10-20 11:11 ` Jozsef Kadlecsik
2003-10-20 6:58 ` Harald Welte
2003-10-19 14:54 Harald Welte
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=3F942CB6.5060005@trash.net \
--to=kaber@trash.net \
--cc=hno@marasystems.com \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.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.