[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <502CF5A2.6000902@panasas.com>
Date: Thu, 16 Aug 2012 16:29:06 +0300
From: Boaz Harrosh <bharrosh@...asas.com>
To: <dedekind1@...il.com>
CC: Marco Stornelli <marco.stornelli@...il.com>, <bhalevy@...ian.com>,
<jack@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>,
<adilger.kernel@...ger.ca>, <tytso@....edu>,
<hirofumi@...l.parknet.co.jp>, <mikulas@...ax.karlin.mff.cuni.cz>,
Al Viro <viro@...IV.linux.org.uk>, <hch@...radead.org>,
<dushistov@...l.ru>, <osd-dev@...n-osd.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
<linux-ext4@...r.kernel.org>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH 2/8] exofs: remove lock/unlock super
On 08/16/2012 04:30 PM, Artem Bityutskiy wrote:
> On Thu, 2012-08-16 at 16:15 +0300, Boaz Harrosh wrote:
>> There are some optimizations I can do here, but lets for now just do
>> the sb->s_lock thing, and I might decide to completely revamp the
>> all thing later.
>
> OK. But I guess an exofs-specific mutex could be used instead. We do not
> have to depend on 'sb->s_lock'.
>
sorry I meant sbi->s_lock. But I'm fine with the complete drop now
Thanks
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists