From: Joe Thornber <joe@fib011235813.fsnet.co.uk>
To: lvm-devel@sistina.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [lvm-devel] [PATCH] add kobject to struct mapped_device
Date: Mon, 30 Dec 2002 10:57:15 +0000 [thread overview]
Message-ID: <20021230105715.GC2703@reti> (raw)
In-Reply-To: <20021220174952.GB12128@kroah.com>
On Fri, Dec 20, 2002 at 09:49:52AM -0800, Greg KH wrote:
> I saw that logic. I don't think sysfs can handle poll right now, but we
> could modify the last access/modify/change time when the status changes
> so stat(2) can be used on the file. This is how usbfs currently
> notifies userspace of changes to their files. Would this be acceptable?
Blech. The nice thing about a blocking operation like poll is that
the process doesn't keep getting rescheduled to check if there is
anything to do.
- Joe
prev parent reply other threads:[~2002-12-30 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 18:43 [PATCH] add kobject to struct mapped_device Greg KH
2002-12-18 18:53 ` [lvm-devel] " Greg KH
2002-12-19 10:55 ` Joe Thornber
2002-12-20 8:31 ` Greg KH
2002-12-20 9:44 ` Joe Thornber
2002-12-20 17:49 ` Greg KH
2002-12-30 10:57 ` Joe Thornber [this message]
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=20021230105715.GC2703@reti \
--to=joe@fib011235813.fsnet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lvm-devel@sistina.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