From: di wang <di.wang@sun.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] OSD iterator interface
Date: Thu, 02 Apr 2009 16:08:18 -0400 [thread overview]
Message-ID: <49D51B32.2020404@sun.com> (raw)
In-Reply-To: <E14DEA02-826C-4F15-8A22-9FA616EFDBC4@Sun.COM>
Hello,
In new MDS stack, osd suppose do not understand Directory (IMHO), and it
only provides
index API. MDD will use the index API to fill the dir entries.
The filldir in current EA index API is just for compatible with old version
of MDS. Maybe we need bulk index API for readdir ? But Alex should
know more.
Thanks
WangDi
Oleg Drokin wrote:
> Hello!
>
> While inspecting patches in bug 17560 it struck me as odd that we
> are fetching the data one entry at a time from the filesystem, so I
> asked a many-entries at a time
> approach to be implemented. Now the patch in the bug just fills
> the osd buffer with entries (after parsing them) and then actual user
> (e.g. __mdd_readpage)
> reparses the osd buffer and copies data to its own. This is a lot
> of wasted processing, copies and then some extra memory usage.
> So in my opinion the iterator interface should be reworked to
> accept an iterator and a buffer and then __mdd_readdir will pass in
> its own
> parsing of the data (with possible generalized preparsing from osd
> so that we are fs-neutral) and will directly fill its own buffer to
> the amount it actually needs,
> kind of like any kernel filldir functions already work right now.
>
> Am I missing something stupid? Are there any objections, would
> this break anything?
>
> Bye,
> Oleg
> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel
>
next prev parent reply other threads:[~2009-04-02 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 18:47 [Lustre-devel] OSD iterator interface Oleg Drokin
2009-04-02 20:08 ` di wang [this message]
2009-04-06 7:21 ` Alex Zhuravlev
2009-04-06 7:43 ` Nikita Danilov
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=49D51B32.2020404@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.