From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lee Ward Date: Thu, 10 Sep 2009 14:10:12 -0600 Subject: [Lustre-devel] Multithreaded liblustre In-Reply-To: <86344224-0630-481D-B40F-87ED6D18D408@Sun.COM> References: <68880AC1-3DDB-4B20-AE49-55227D64F295@swedisk.se> <1252609385.3953.41.camel@wheel> <86344224-0630-481D-B40F-87ED6D18D408@Sun.COM> Message-ID: <1252613412.3953.42.camel@wheel> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lustre-devel@lists.lustre.org On Thu, 2009-09-10 at 13:06 -0600, Oleg Drokin wrote: > Hello! > > On Sep 10, 2009, at 3:03 PM, Lee Ward wrote: > >> 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. > > Well, there are many sides to "multithreaded", that's why I am asking. > Good to know. > > > But... I thought SUN had dropped support for liblustre entirely? Did I > > miss something? > > Liblustre is still a first class citizen, fully supported in HEAD (2.0) > codebase too, tested along with other stuff at scheduled intervals in > our testsuite. > > I don't even remember anybody proposing dropping liblustre support in > recent times. I did and, it turns out, I was mistaken. Thanks. --Lee > > Bye, > Oleg >