Lustre-devel archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Zhuravlev <Alex.Zhuravlev@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] SOM questions
Date: Mon, 11 Jan 2010 19:44:38 +0300	[thread overview]
Message-ID: <4B4B5576.2090405@sun.com> (raw)
In-Reply-To: <4B4B4801.7070509@sun.com>

On 1/11/10 6:47 PM, Alex Zhuravlev wrote:
> it looks quite simple and with very minimal changes to existing protocol
> logic. I also think that following this we don't need dedicated IO epoch
> notion and can use regular VBR version increasing on each open.

sorry, I forgot to add that all this essentially means no SOM-specific
in-core state on MDS at all and no need to maintain in-core state over
reboots.

thanks, Alex

  reply	other threads:[~2010-01-11 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 18:01 [Lustre-devel] SOM questions Eric Barton
2010-01-06 16:51 ` Aleksandr Guzovskiy
2010-01-11 14:10 ` Vitaly Fertman
2010-01-11 15:47   ` Alex Zhuravlev
2010-01-11 16:44     ` Alex Zhuravlev [this message]
2010-01-11 21:59     ` Vitaly Fertman
2010-01-12  3:42       ` Alex Zhuravlev

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=4B4B5576.2090405@sun.com \
    --to=alex.zhuravlev@sun.com \
    --cc=lustre-devel@lists.lustre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox