netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anil Gunturu <anil.gunturu@gmail.com>
To: netdev@oss.sgi.com
Subject: NETLINK_ROUTE sockets in kernel
Date: Tue, 2 Nov 2004 11:46:46 -0800	[thread overview]
Message-ID: <2f61ba570411021146657f63f4@mail.gmail.com> (raw)

Hi,
I am trying to undestand the NETLINK_ROUTE protocol sockets on 2.4.18
kernel. Specifically, I am interested in knowing how the kernel
processes the netlink messages that it recieves from user space. I was
browsing the rtnetlink_rcv_msg (net/core/rtnetlink.c) function in the
kernel. But its not clear on how the rtnetlink_links array is
populated for PF_NETLINK family. rtnetlink_init seem to populate for
PF_PACKET and PF_UNSPEC.
Thanks,
-Anil

             reply	other threads:[~2004-11-02 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02 19:46 Anil Gunturu [this message]
2004-11-02 21:22 ` NETLINK_ROUTE sockets in kernel David S. Miller
2004-11-02 21:44 ` John W. Linville
2004-11-03  0:52   ` Neil Horman
2004-11-02 22:15 ` Herbert Xu

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=2f61ba570411021146657f63f4@mail.gmail.com \
    --to=anil.gunturu@gmail.com \
    --cc=netdev@oss.sgi.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 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).