From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: ARAI Shun-ichi <hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Which version of nilfs do you use?
Date: Fri, 28 Dec 2012 12:17:39 +0400 [thread overview]
Message-ID: <1356682659.2126.23.camel@slavad-ubuntu> (raw)
In-Reply-To: <20121228.165816.981117143166927771.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
On Fri, 2012-12-28 at 16:58 +0900, ARAI Shun-ichi wrote:
> In <1356675289.2126.10.camel@slavad-ubuntu>;
> Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org> wrote
> as Subject "Re: Which version of nilfs do you use?":
>
> > I think that it can be a synchronization issue. But it needs to
> > investigate the situation more deeply. As I can see, it is using 8 CPUs
> > in the case of the issue and it takes place frequent update. So, it can
> > be a ground for good issue reproducibility, from my point of view.
>
> CPU of my PC is Core i7 3770S. It has 4 cores with HTT (8 threads).
And you had the issue also. But I tried to reproduce on 2 cores CPU
(without success currently). So, in the case of synchronization issue a
count of CPUs' cores can be a important factor, I think. And
unfortunately, currently, we haven't clear and easy way of the issue
reproducing.
With the best regards,
Vyacheslav Dubeyko.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-12-28 8:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 9:47 Which version of nilfs do you use? Elmer Zhang
[not found] ` <AAEC3976-3D79-4170-B1DC-2A04499392DE-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-27 10:35 ` dexen deVries
2012-12-28 2:20 ` Elmer Zhang
[not found] ` <BB9A0F28-A902-4FE4-BA58-A66EA93290F8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-28 2:58 ` ARAI Shun-ichi
[not found] ` <20121228.115843.568913897223506746.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
2012-12-28 6:14 ` Vyacheslav Dubeyko
2012-12-28 7:58 ` ARAI Shun-ichi
[not found] ` <20121228.165816.981117143166927771.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
2012-12-28 8:17 ` Vyacheslav Dubeyko [this message]
2012-12-28 6:06 ` Vyacheslav Dubeyko
2012-12-28 7:12 ` Elmer Zhang
[not found] ` <948BD9D2-CAF2-444D-A23B-00D689BA69CE-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-28 7:33 ` Vyacheslav Dubeyko
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=1356682659.2126.23.camel@slavad-ubuntu \
--to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
--cc=hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.