From: Lee Ward <lee@sandia.gov>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Multithreaded liblustre
Date: Thu, 10 Sep 2009 13:03:05 -0600 [thread overview]
Message-ID: <1252609385.3953.41.camel@wheel> (raw)
In-Reply-To: <EBD3008A-44E8-4A1E-A642-4777F7D206C7@sun.com>
On Thu, 2009-09-10 at 12:39 -0600, Oleg Drokin wrote:
> Hello!
>
> On Sep 10, 2009, at 8:52 AM, Tuve Nordius wrote:
> > Does anyone know what need to be done/ the main obstacles in order to
> > make liblustre multithreaded?
>
> What sort of multi-threadness are you looking at?
> Currently socklnd has separate threads if I remember right.
> There are no callbacks and other async stuff happening, but that is
> pretty much by design so would be hard to change.
If you are talking about the API, the current head for SYSIO is
thread-safe for all but initialization, mount, unmount, and shutdown.
Don't think it works for liblustre at present, but rklundt at sandia.gov is
currently doing a port, maybe done already.
Re-entrancy is to be supported some time in 2010.
But... I thought SUN had dropped support for liblustre entirely? Did I
miss something?
--Lee
>
> 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-09-10 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 12:52 [Lustre-devel] Multithreaded liblustre Tuve Nordius
2009-09-10 18:39 ` Oleg Drokin
2009-09-10 19:03 ` Lee Ward [this message]
2009-09-10 19:06 ` Oleg Drokin
2009-09-10 19:59 ` Tuve Nordius
2009-09-15 3:22 ` Lee Ward
2009-09-10 20:10 ` Lee Ward
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=1252609385.3953.41.camel@wheel \
--to=lee@sandia.gov \
--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.