From: Mike Galbraith <bitbucket@online.de>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: akpm@linux-foundation.org, manfred@colorfullife.com,
riel@redhat.com, aswin@hp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] ipc,msg: document barriers
Date: Sat, 11 Jan 2014 05:18:51 +0100 [thread overview]
Message-ID: <1389413931.6068.5.camel@marge.simpson.net> (raw)
In-Reply-To: <1389379707-20298-8-git-send-email-davidlohr@hp.com>
On Fri, 2014-01-10 at 10:48 -0800, Davidlohr Bueso wrote:
> Both expunge_all() and pipeline_send() rely on both a nil msg value and a
> full barrier to guarantee the correct ordering when waking up a task. While
> its counter part at the receiving end is well documented for the lockless
> recv algorithm, we still need to document these specific smp_mb() calls.
>
> Signed-off-by: Davidlohr Bueso <davidlohr@hp.com>
> ---
> ipc/msg.c | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/ipc/msg.c b/ipc/msg.c
> index 4377f4a..8c1cc76 100644
> --- a/ipc/msg.c
> +++ b/ipc/msg.c
> @@ -253,8 +253,14 @@ static void expunge_all(struct msg_queue *msq, int res)
> struct msg_receiver *msr, *t;
>
> list_for_each_entry_safe(msr, t, &msq->q_receivers, r_list) {
> - msr->r_msg = NULL;
> + msr->r_msg = NULL; /* initialize expunge ordering */
> wake_up_process(msr->r_tsk);
> + /*
> + * Ensure that the wakeup is visible before setting r_msg as
> + * the receiving end depends on it: either spinning on a nil,
> + * or dealing with -EAGAIN cases. See lockless reveice part 1
^^^^^^^ lysdexic fingers
> + * and 2 in do_msgrcv().
> + */
> smp_mb();
> msr->r_msg = ERR_PTR(res);
> }
> @@ -638,15 +644,22 @@ static inline int pipelined_send(struct msg_queue *msq, struct msg_msg *msg)
>
> list_del(&msr->r_list);
> if (msr->r_maxsize < msg->m_ts) {
> + /* initialize pipelined send ordering */
> msr->r_msg = NULL;
> wake_up_process(msr->r_tsk);
> - smp_mb();
> + smp_mb(); /* see barrier comment below */
> msr->r_msg = ERR_PTR(-E2BIG);
> } else {
> msr->r_msg = NULL;
> msq->q_lrpid = task_pid_vnr(msr->r_tsk);
> msq->q_rtime = get_seconds();
> wake_up_process(msr->r_tsk);
> + /*
> + * Ensure that the wakeup is visible before
> + * setting r_msg, as the receiving end depends
> + * on it. See lockless reveice part 1 and 2 in
^^^^^^^ ditto
next prev parent reply other threads:[~2014-01-11 4:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 18:48 [PATCH -next 0/7] ipc: some misc updates & optimizations Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 1/7] ipc: standardize code comments Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 2/7] ipc: remove braces for single statements Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 3/7] ipc: remove useless return statement Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 4/7] ipc: simplify sysvipc_proc_open return Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 5/7] ipc: delete seq_max field in struct ipc_ids Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 6/7] ipc: share ids rwsem when possible in ipcget_public Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 7/7] ipc,msg: document barriers Davidlohr Bueso
2014-01-11 4:18 ` Mike Galbraith [this message]
2014-01-11 9:02 ` [PATCH -next 0/7] ipc: some misc updates & optimizations Manfred Spraul
2014-01-11 17:54 ` Davidlohr Bueso
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=1389413931.6068.5.camel@marge.simpson.net \
--to=bitbucket@online.de \
--cc=akpm@linux-foundation.org \
--cc=aswin@hp.com \
--cc=davidlohr@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=riel@redhat.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
Powered by JetHome