mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Jay Lan <jlan@engr.sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Guillaume Thouvenin <guillaume.thouvenin@bull.net>,
	greg@kroah.com, linux-kernel@vger.kernel.org,
	efocht@hpce.nec.com, linuxram@us.ibm.com, gh@us.ibm.com,
	elsa-devel@lists.sourceforge.net, aquynh@gmail.com,
	dean-list-linux-kernel@arctic.org, pj@sgi.com
Subject: Re: [patch 2.6.12-rc1-mm4] fork_connector: add a fork connector
Date: Mon, 11 Apr 2005 10:44:56 +0400	[thread overview]
Message-ID: <20050411104456.A31664@2ka.mipt.ru> (raw)
In-Reply-To: <425A0E7C.8080900@engr.sgi.com>; from jlan@engr.sgi.com on Sun, Apr 10, 2005 at 10:43:24PM -0700

On Sun, Apr 10, 2005 at 10:43:24PM -0700, Jay Lan (jlan@engr.sgi.com) wrote:
> I based my listen program on the fclisten.c posted by Kaigai Kohei
> with my own modification. Unfortunately i lost my test machine in the
> lab. I will recreate the listen program Monday. The original listener
> did not validate sequence number. It also prints length of data and
> sequence number of every message it receives. My listener prints
> only out-of-sequence error messages.
> 
> The fork generator fork-test.c was yours? I called it fork-test
> and let it run continuously in while-loop:
> 
> # while 1
> # ./fork-test 10000000
> # sleep 1
> # end
> 
> I let it do 10,000,000 times of fork continuously while the system
> is running AIM7 and/or ubench.
> 
> The original fclisten.c and fork-test.c are attached for your reference.

It is pretty normal to see duplicated numbers in a fork test - 
I observed it too, since counter is incremented without locks
we can catch situation when it is incremented simultaneously 
on both processors, the latest version of the fork connector
from Guillaume contains processor id in the message and per cpu counters, 
so one can destinguish messages which sequence numbers will flow
in a very similar way now.

> - jay
> 

-- 
	Evgeniy Polyakov

  reply	other threads:[~2005-04-11  6:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31 13:59 Guillaume Thouvenin
2005-03-31 22:44 ` Andrew Morton
2005-04-01  0:10   ` Jay Lan
2005-04-01  7:52     ` Evgeniy Polyakov
2005-04-07 22:40       ` Jay Lan
2005-04-07 22:47         ` Jay Lan
2005-04-08 10:24           ` Evgeniy Polyakov
2005-04-08 10:52             ` Evgeniy Polyakov
2005-04-08 20:27               ` Jay Lan
2005-04-08 22:08                 ` Jay Lan
2005-04-08 22:18                   ` Evgeniy Polyakov
2005-04-09  3:31                     ` Jay Lan
2005-04-09  6:29                       ` Evgeniy Polyakov
2005-04-11  5:43                         ` Jay Lan
2005-04-11  6:44                           ` Evgeniy Polyakov [this message]
2005-04-11  6:51                             ` Andrew Morton
2005-04-11  7:31                               ` Evgeniy Polyakov
2005-03-31 22:53 ` Andrew Morton
2005-04-01 10:56 ` Guillaume Thouvenin

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=20050411104456.A31664@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=akpm@osdl.org \
    --cc=aquynh@gmail.com \
    --cc=dean-list-linux-kernel@arctic.org \
    --cc=efocht@hpce.nec.com \
    --cc=elsa-devel@lists.sourceforge.net \
    --cc=gh@us.ibm.com \
    --cc=greg@kroah.com \
    --cc=guillaume.thouvenin@bull.net \
    --cc=jlan@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxram@us.ibm.com \
    --cc=pj@sgi.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

all inboxes | Powered by JetHome®