From: Corey Minyard <cminyard@mvista.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH} Network interface for IPMI
Date: Wed, 17 Nov 2004 15:19:10 -0600 [thread overview]
Message-ID: <419BC04E.7050004@mvista.com> (raw)
In-Reply-To: <20041117125114.0c8fdf62.akpm@osdl.org>
Andrew Morton wrote:
>Corey Minyard <cminyard@mvista.com> wrote:
>
>
>>IPMI is a manage standard that allows intelligent management controllers
>>to monitor things about the system (temperature, fan speed, etc.). The
>>management controllers sit on a bus, and have addresses, and such.
>>After seeing the ugliness required for the 32-bit ioctl compatability
>>layers for 64-bit kernels, I have decided that the network interface for
>>IPMI is a good thing, as the IPMI device ioctls have pointers and
>>require ugly hacks. None should be needed for the network interface.
>>
>>This patch adds that layer.
>>
>>-#define NPROTO 32 /* should be enough for now.. */
>>+#define NPROTO 64 /* should be enough for now.. */
>>
>>
>
>Boy, that was a big bump. Was this intentional?
>
>
It's the next power of 2 :). Any value larger than 32 should work, I'll
just set it to 33.
>
>
>>+static struct ipmi_sock *ipmi_socket_create1(struct socket *sock)
>>+{
>>+ struct ipmi_sock *i;
>>+
>>+ if (atomic_read(&ipmi_nr_socks) >= 2*files_stat.max_files)
>>+ return NULL;
>>
>>
>
>Why this test?
>
>
It snuck in from the original patch writer and I missed it. Not necessary.
>
>
>>+config IPMI_SOCKET
>>+ tristate "IPMI sockets"
>>+ depends on IPMI_HANDLER
>>+ ---help---
>>+ If you say Y here, you will include support for IPMI sockets;
>>+ This way you don't have to use devices to access IPMI. You
>>+ must also enable the IPMI message handler and a low-level
>>+ driver in the Character Drivers if you enable this.
>>+
>>+ If unsure, say N.
>>
>>
>
>Is this new kernel interface documented somewhere?
>
>
I thought I had done it, but it doesn't appear to be there. I'll add
some and repost a patch.
Thanks,
-Corey
next prev parent reply other threads:[~2004-11-17 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 20:36 [PATCH} Network interface for IPMI Corey Minyard
2004-11-17 20:51 ` Andrew Morton
2004-11-17 21:19 ` Corey Minyard [this message]
2004-11-17 22:12 ` Corey Minyard
[not found] <31Fe2-5kB-11@gated-at.bofh.it>
2004-11-18 4:36 ` Andi Kleen
2004-11-18 14:09 ` Corey Minyard
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=419BC04E.7050004@mvista.com \
--to=cminyard@mvista.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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 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).