From: Boaz Harrosh <bharrosh@panasas.com>
To: <dedekind1@gmail.com>
Cc: Marco Stornelli <marco.stornelli@gmail.com>, <bhalevy@tonian.com>,
<jack@suse.cz>, Andrew Morton <akpm@linux-foundation.org>,
<adilger.kernel@dilger.ca>, <tytso@mit.edu>,
<hirofumi@mail.parknet.co.jp>, <mikulas@artax.karlin.mff.cuni.cz>,
Al Viro <viro@ZenIV.linux.org.uk>, <hch@infradead.org>,
<dushistov@mail.ru>, <osd-dev@open-osd.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
<linux-ext4@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 2/8] exofs: remove lock/unlock super
Date: Thu, 16 Aug 2012 16:29:06 +0300 [thread overview]
Message-ID: <502CF5A2.6000902@panasas.com> (raw)
In-Reply-To: <1345123814.3393.237.camel@sauron.fi.intel.com>
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
next prev parent reply other threads:[~2012-08-16 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 10:00 [PATCH 2/8] exofs: remove lock/unlock super Marco Stornelli
2012-08-16 12:20 ` Artem Bityutskiy
2012-08-16 12:32 ` Boaz Harrosh
2012-08-16 13:10 ` Artem Bityutskiy
2012-08-16 13:15 ` Boaz Harrosh
2012-08-16 13:23 ` Boaz Harrosh
2012-08-16 13:30 ` Artem Bityutskiy
2012-08-16 13:29 ` Boaz Harrosh [this message]
2012-08-16 16:09 ` Marco Stornelli
2012-08-16 13:23 ` Boaz Harrosh
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=502CF5A2.6000902@panasas.com \
--to=bharrosh@panasas.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=bhalevy@tonian.com \
--cc=dedekind1@gmail.com \
--cc=dushistov@mail.ru \
--cc=hch@infradead.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=osd-dev@open-osd.org \
--cc=tytso@mit.edu \
--cc=viro@ZenIV.linux.org.uk \
/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.