From: Murali Karicheri <m-karicheri2@ti•com>
To: "open list:TI NETCP ETHERNET DRIVER" <netdev@vger•kernel.org>
Subject: SNMP read-write MIBs
Date: Tue, 1 Nov 2016 14:06:40 -0400 [thread overview]
Message-ID: <5818D9B0.60907@ti.com> (raw)
Hello netdev experts,
I am investigating the requirements to support hsr/prp SNMP functions in kernel.
Based on my investigation so far, the kernel include file include/net/snmp.h
defines all of the SNMP MIBS related defines and structures. But the MIBs are
read-only type MIBs. Is there any implementation of read-write MIBs in kernel?
One of the specs for MIBs that are investigating have read-write MIBs and
wondering if we have any precedence of such MIBs implemented in kernel space.
If not, what is the suggested way to implement these MIBs in kernel space?
I assume that to implement read-only MIBs for hsr driver, I need to add
them to snmp.h and use standard Macros in snmp.h to update them from the driver.
Thanks
Murali Karicheri
Linux Kernel, Keystone
next reply other threads:[~2016-11-01 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 18:06 Murali Karicheri [this message]
2016-11-02 14:47 ` SNMP read-write MIBs Murali Karicheri
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=5818D9B0.60907@ti.com \
--to=m-karicheri2@ti$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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