From: Liang Zhen <Zhen.Liang@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Completion callbacks
Date: Wed, 13 Aug 2008 14:32:01 +0800 [thread overview]
Message-ID: <48A27FE1.8080208@sun.com> (raw)
In-Reply-To: <48A2769E.1060001@sun.com>
Liang Zhen ??:
>
> 2. we change ptlrpc_master_callback so that: it makes a copy of EV and
> queue it in a
> FIFO and return, another thread process ev's in this FIFO and callback
> one by one and
> we can guarantee events order and call real callbacks without lnet_lock
>
We can even have an eq_callback_thread (or threads pool) in LNet,
lnet_enq_event_locked() enqueue event and wakeup the callback_thread,
so we don't need change ptlrpc at all.
>
> -devel
>
next prev parent reply other threads:[~2008-08-13 6:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 18:05 [Lustre-devel] Completion callbacks Eric Barton
2008-08-13 3:24 ` Peter Braam
2008-08-13 3:53 ` Nikita Danilov
2008-08-13 5:52 ` Liang Zhen
2008-08-13 6:32 ` Liang Zhen [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-13 11:04 Maxim V. Patlasov
2008-08-13 22:28 ` Peter Braam
2008-08-14 9:28 ` Eric Barton
2008-08-15 2:42 ` Liang Zhen
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=48A27FE1.8080208@sun.com \
--to=zhen.liang@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