From: Christoph Hellwig <hch@lst.de>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Andrew Morton <akpm@osdl.org>,
linux-raid@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH md 1 of 2] Add interface to md driver for userspace monitoring of events.
Date: Mon, 6 Sep 2004 16:02:33 +0200 [thread overview]
Message-ID: <20040906140233.GB20941@lst.de> (raw)
In-Reply-To: <16699.47090.307180.958993@cse.unsw.edu.au>
On Mon, Sep 06, 2004 at 11:05:54AM +1000, Neil Brown wrote:
> > Christoph points out that this is fairly wild procfs abuse. We want to be
> > moving away from that sort of thing, not adding to it.
>
> I guess it depends on what you mean by "wild procfs abuse"...
> Given that /proc/mdstat already exists it doesn't seem too
> unreasonable to add a little functionality to it. How much does it hurt?
poll on procfs is defintily abuse, even in categories of the use procfs
every times.
> > Is it possible to use rml's new event stuff from rc1-mm3's
> > kernel-sysfs-events-layer.patch? Or a bare netlink interface? Or
> > raidfs?
>
> sysfs:
> Probably. I would like to improve sysfs support for md but I
> haven't taken the plunge yet to figure out how it all works.
> kevents may well be ok, but as you may need to handle
> multipath-failed events in times if high memory pressure, and need
> to handle it before pressure can be relieved, I prefer to minimise
> the number of kmallocs needed to get the event to userspace.
>
> bare netlink:
> Probably perter sysfs... Funny, but I remember reading a comment in
> the code (2.4 I think, ages ago) about netlink being deprecated or
> something like that, so I never bothered looking at it. I wonder
> what it meant.
netlink isn't deprecated, netlink_dev (aka netlink as chardevice nodes)
is.
next prev parent reply other threads:[~2004-09-06 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 2:27 [PATCH md 0 of 2] Introduction NeilBrown
2004-09-03 2:27 ` [PATCH md 2 of 2] Correct "working_disk" counts for raid5 and raid6 NeilBrown
2004-09-03 2:27 ` [PATCH md 1 of 2] Add interface to md driver for userspace monitoring of events NeilBrown
2004-09-03 10:19 ` Andrew Morton
2004-09-06 1:05 ` Neil Brown
2004-09-06 14:02 ` Christoph Hellwig [this message]
2004-09-06 22:53 ` Neil Brown
2004-09-06 23:07 ` Andrew Morton
2004-09-07 0:53 ` Neil Brown
2004-09-07 10:45 ` Christoph Hellwig
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=20040906140233.GB20941@lst.de \
--to=hch@lst.de \
--cc=akpm@osdl.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).