[Lustre-devel] releasing BKL in lustre_fill_super

Jeremy Filizetti jeremy.filizetti at gmail.com
Thu Dec 16 05:47:57 PST 2010

On Wed, Nov 10, 2010 at 5:40 AM, Andreas Dilger
<andreas.dilger at oracle.com>wrote:

> On 2010-11-09, at 08:55, Jeremy Filizetti wrote:
> >> The first thing I always think about when seeing a problem like this is
> not "how to reduce this contention" but "do we need to be doing this at
> all"?
> >
> > I can't really answer whether "we need to do it",  but I can elaborate on
> what is happening.  The actual write that is being done during the
> lustre_process_log is when the llog is being copied from the remote server
> to the local server.  I assume this is at least a necessary step and no
> getting rid of the llog without some sort of overhaul.
> In fact, this config llog copying should only be done on the first mount of
> the OST, or if the configuration has changed.
> We've actually removed this entirely for the 2.4 release, though that
> doesn't help you now.

Does that mean the llog component of Lustre is completely removed?  Is 2.4
an Oracle only release?

> Cheers, Andreas
> --
> Andreas Dilger
> Lustre Technical Lead
> Oracle Corporation Canada Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20101216/6157addc/attachment.htm>

More information about the lustre-devel mailing list