From: Davide Libenzi <davidel@xmailserver.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Eric Van Hensbergen <ericvh@gmail.com>,
Ron Minnich <rminnich@sandia.gov>, Ingo Molnar <mingo@elte.hu>,
Christoph Hellwig <hch@infradead.org>,
Miklos Szeredi <mszeredi@suse.cz>,
Brad Boyer <flar@allandria.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Roland McGrath <roland@redhat.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] poll: allow f_op->poll to sleep, take#5
Date: Tue, 25 Nov 2008 22:27:38 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.1.10.0811252148540.32523@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <492CD358.2020603@gmail.com>
On Wed, 26 Nov 2008, Tejun Heo wrote:
> +static int pollwake(wait_queue_t *wait, unsigned mode, int sync, void *key)
> +{
> + struct poll_wqueues *pwq = wait->private;
> + DECLARE_WAITQUEUE(dummy_wait, pwq->polling_task);
> +
> + /*
> + * Wake up functions have full barrier semantics, no need for
> + * barrier here.
> + */
> + pwq->triggered = 1;
> +
> + /*
> + * Perform the default wake up operation using a dummy
> + * waitqueue.
> + *
> + * TODO: This is hacky but there currently is no interface to
> + * pass in @sync. @sync is scheduled to be removed and once
> + * that happens, wake_up_process() can be used directly.
> + */
> + return default_wake_function(&dummy_wait, mode, sync, key);
> +}
> +int poll_schedule_timeout(struct poll_wqueues *pwq, int state,
> + ktime_t *expires, unsigned long slack)
> +{
> + int rc = -EINTR;
> +
> + set_current_state(state);
> + if (!pwq->triggered)
> + rc = schedule_hrtimeout_range(expires, slack, HRTIMER_MODE_ABS);
> + __set_current_state(TASK_RUNNING);
> +
> + /*
> + * Prepare for the next iteration. ->poll() might not have
> + * enough barrier semantics from the second round as waits are
> + * registered only during the first one. Use set_mb().
> + */
> + set_mb(pwq->triggered, 0);
> +
> + return rc;
> +}
> +EXPORT_SYMBOL(poll_schedule_timeout);
Look, pollwake() does:
w1) WR triggered (1)
w2) WMB
w3) WR task->state (RUNNING)
While poll_schedule_timeout() does:
s1) WR task->state (TASK_INTERRUPTIBLE)
s2) MB
s3) RD triggered
s4) IF0 => RD task->state (if !RUNNING -> sleep)
The only risk is that w3 preceed s1, so that we go to sleep even though a
wakeup has been issued. But if w3 is visible, w1 is visible too, that
means that 'triggered' is visible in s3 (there's a MB in s2). So we skip
the schedule_hrtimeout_range(). So IMO you need no barriers on 'triggered'.
If you feel you need barriers, do you mind explaning a sequence of events
that makes a barrier-free version break?
- Davide
next prev parent reply other threads:[~2008-11-26 6:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 17:30 + poll-allow-f_op-poll-to-sleep-take-4.patch added to -mm tree Oleg Nesterov
2008-11-25 21:08 ` Davide Libenzi
2008-11-26 4:33 ` Tejun Heo
2008-11-26 4:40 ` [PATCH] poll: allow f_op->poll to sleep, take#5 Tejun Heo
2008-11-26 6:27 ` Davide Libenzi [this message]
2008-11-26 6:39 ` Tejun Heo
2008-11-26 19:36 ` Davide Libenzi
2008-11-27 9:18 ` Tejun Heo
2008-11-27 9:37 ` [PATCH] poll: allow f_op->poll to sleep, take#6 Tejun Heo
2008-11-28 4:35 ` Davide Libenzi
2008-11-28 4:44 ` Tejun Heo
2008-11-28 16:08 ` Oleg Nesterov
2008-11-27 20:13 ` [PATCH] poll: allow f_op->poll to sleep, take#5 Oleg Nesterov
2008-11-26 4:49 ` + poll-allow-f_op-poll-to-sleep-take-4.patch added to -mm tree Tejun Heo
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=alpine.DEB.1.10.0811252148540.32523@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=akpm@linux-foundation.org \
--cc=ericvh@gmail.com \
--cc=flar@allandria.com \
--cc=hch@infradead.org \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
--cc=mszeredi@suse.cz \
--cc=oleg@redhat.com \
--cc=rminnich@sandia.gov \
--cc=roland@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®