From: Tobias DiPasquale <codeslinger@gmail.com>
To: Silimite <silimite@gmail.com>
Cc: netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: Handling large amounts of data
Date: Sun, 15 May 2005 18:15:13 -0400 [thread overview]
Message-ID: <876ef97a05051515154bdb4157@mail.gmail.com> (raw)
In-Reply-To: <5ad977d10505151446348e932f@mail.gmail.com>
On 5/15/05, Silimite <silimite@gmail.com> wrote:
> My question is, what is the best way to communicate all these ranges
> from user-space into the kernel module? I am currently loading them
> via procfs. Is this an acceptable method or should I be looking at
> something else? It certainly works great but I would like it to be as
> "proper" as possible.
A unicast netlink socket would almost certainly be the best way to go
here. For examples on how to use unicast netlink sockets, look at
net/ipv4/netfilter/ip_queue.c or net/core/rtnetlink.c.
--
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d
next prev parent reply other threads:[~2005-05-15 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 21:46 Handling large amounts of data Silimite
2005-05-15 22:15 ` Tobias DiPasquale [this message]
2005-05-16 14:39 ` Silimite
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=876ef97a05051515154bdb4157@mail.gmail.com \
--to=codeslinger@gmail.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=silimite@gmail.com \
/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.