All of lore.kernel.org
 help / color / mirror / Atom feed
From: di wang <di.wang@sun.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] [RFC] two ideas for Meta Data Write Back Cache
Date: Mon, 06 Apr 2009 18:02:14 -0400	[thread overview]
Message-ID: <49DA7BE6.6070006@sun.com> (raw)
In-Reply-To: <m3zleu5b8f.fsf@bzzz.home.net>


> 2) "create w/o name" (this is what MDT accepts these days) isn't operation,
>    it's partial operation. but for partial operations we already have OSD
>    - clear, simple and generic. having one more "partial operations" adds
>    nothing besides confusion, IMHO
>   
I am not sure you can( or should) translate all the MD partial 
operation  into object  RPC for these partial
MD operation.  For example rename,  (a/b  ---> c/d,  a/b in MDS1, c/d in 
MDS2).

     RPC goes to MDS1.

     1) delete d (entry and object) from c in MDS2.
     2) create b entry under c in MDS2.
     3) delete b entry under a in MDS1.

So if you do 1) and 2) by object rpc (skip mdd), then you might need 
create create all 4 objects
(a and b are local object, c and d are remote object),  and permission 
check locally (whether
you can delete d under c). Not sure it is a good way.  And also some 
quota stuff are handled
in these partial operation in remote MDD, so I am not sure we should 
skip mdd totally here.
Am I miss sth?

Thanks
WangDi

  reply	other threads:[~2009-04-06 22:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06  9:39 [Lustre-devel] [RFC] two ideas for Meta Data Write Back Cache Alexander Zarochentsev
2009-04-06 10:03 ` Andreas Dilger
2009-04-06 10:26   ` Alex Zhuravlev
2009-04-06 22:02     ` di wang [this message]
2009-04-07  4:27       ` Alex Zhuravlev
2009-05-18 21:01         ` Eric Barton
  -- strict thread matches above, loose matches on Subject: below --
2009-04-05 20:50 Alexander Zarochentsev

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=49DA7BE6.6070006@sun.com \
    --to=di.wang@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 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.