All of lore.kernel.org
 help / color / mirror / Atom feed
From: srinivas eeda <srinivas.eeda@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 3/3] o2net: correct keepalive message protocol
Date: Wed, 17 Feb 2010 17:46:50 -0800	[thread overview]
Message-ID: <4B7C9C0A.1040502@oracle.com> (raw)
In-Reply-To: <4B7C9310.6050201@oracle.com>

whenever a message is received o2net_process_message will call 
o2net_sc_postpone_idle to cancel/requeue keepalive message. What will 
happen if the 2 seconds have passed right before the cancel was issued. 
Will the work gets queued which will be executed later by o2net thread 
or will o2net thread gets interrupted and will execute this work? or can 
both codes be executed in parallel?

On 2/17/2010 5:08 PM, Sunil Mushran wrote:
> srinivas eeda wrote:
>> Ok, I'll modify the patch. Are messages queued on o2net_wq and 
>> execution of o2net_process_message is always done in the context of 
>> o2net thread and are synchronized?
>>
> o2net is the context. Synchronized?

  reply	other threads:[~2010-02-18  1:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-29  4:51 [Ocfs2-devel] o2net patches Srinivas Eeda
2010-01-29  4:51 ` [Ocfs2-devel] [PATCH 1/3] o2net: rollback reconnect on network timeout Srinivas Eeda
2010-01-29  4:51 ` [Ocfs2-devel] [PATCH 2/3] o2net: delay enotconn for sends receives till quorum decision Srinivas Eeda
2010-01-29  4:51 ` [Ocfs2-devel] [PATCH 3/3] o2net: correct keepalive message protocol Srinivas Eeda
2010-02-17  5:56   ` Joel Becker
2010-02-17 18:24     ` Srinivas Eeda
2010-02-17 22:40       ` Sunil Mushran
2010-02-17 22:52         ` Srinivas Eeda
2010-02-17 22:47           ` Sunil Mushran
2010-02-17 23:45             ` Srinivas Eeda
2010-02-17 23:50               ` Sunil Mushran
2010-02-18  0:59                 ` srinivas eeda
2010-02-18  1:08                   ` Sunil Mushran
2010-02-18  1:46                     ` srinivas eeda [this message]
2010-02-18  1:49       ` Joel Becker
2010-02-18  1:55         ` srinivas eeda

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=4B7C9C0A.1040502@oracle.com \
    --to=srinivas.eeda@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.