From: Andrew Morton <akpm@linux-foundation.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] support polling of /proc/swaps
Date: Tue, 19 Oct 2010 16:38:37 -0700 [thread overview]
Message-ID: <20101019163837.c2a67d0b.akpm@linux-foundation.org> (raw)
In-Reply-To: <1287530747.1171.9.camel@yio.site>
On Wed, 20 Oct 2010 01:25:47 +0200
Kay Sievers <kay.sievers@vrfy.org> wrote:
> On Tue, 2010-10-19 at 15:31 -0700, Andrew Morton wrote:
> > On Tue, 19 Oct 2010 11:19:16 +0200
> > Kay Sievers <kay.sievers@vrfy.org> wrote:
>
> > It's a bit sad that we have to add quite a pile of infrastructure to
> > make a procfs file pollable. I wonder if it's possible to provide some
> > core support for this, and reduce the amount of code at each particular
> > handler site.
>
> You mean something like adding the event counter to the seq_file? There
> is /proc/self/mounts,mountinfo and /proc/swaps so far, I think.
Don't know - I was just waving hands about wondering if we really need
to add 48 new lines of code each time we want to make a procfs file
pollable.
> > Also, I wonder how we are to communicate the existence of this feature
> > to our users. Nobody will look in Documentation/filesystems/. Is
> > there a manpage? Seems not...
>
> Hmm, 'man 5 proc'?
yes, that mentions /proc/swaps.
> > > +static DECLARE_WAIT_QUEUE_HEAD(proc_poll_wait);
> > > +static int proc_poll_event;
> >
> > Please pick a lock to protect proc_poll_event.
>
> An atomic_t should do it too, right?
It does.
> > Then document that
> > locking here, when you also document proc_poll_event ;)
>
> The actual value has no meaning at all, it just tells that something
> happened if it has changed.
>
bah.
--- a/mm/swapfile.c~proc-swaps-support-polling-fix
+++ a/mm/swapfile.c
@@ -60,6 +60,7 @@ static struct swap_info_struct *swap_inf
static DEFINE_MUTEX(swapon_mutex);
static DECLARE_WAIT_QUEUE_HEAD(proc_poll_wait);
+/* Activity counter to indicate that a swapon or swapoff has occurred */
static atomic_t proc_poll_event = ATOMIC_INIT(0);
static inline unsigned char swap_count(unsigned char ent)
_
next prev parent reply other threads:[~2010-10-19 23:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 9:19 [PATCH] support polling of /proc/swaps Kay Sievers
2010-10-19 11:09 ` Peter Zijlstra
2010-10-19 16:11 ` Jonathan Corbet
2010-10-19 18:54 ` Kay Sievers
2010-10-19 22:31 ` Andrew Morton
2010-10-19 23:25 ` Kay Sievers
2010-10-19 23:38 ` Andrew Morton [this message]
2010-11-15 3:44 ` Neil Brown
2010-11-16 15:56 ` Kay Sievers
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=20101019163837.c2a67d0b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.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