linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Curt Wohlgemuth <curtw@google.com>
To: Andreas Dilger <adilger@sun.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 2/2] ext4: Handle nested ext4_journal_start/stop calls without a journal
Date: Fri, 18 Sep 2009 11:33:04 -0700	[thread overview]
Message-ID: <6601abe90909181133g27458301nb3aae756e473541c@mail.gmail.com> (raw)
In-Reply-To: <20090918055010.GN2537@webber.adilger.int>

On Thu, Sep 17, 2009 at 10:50 PM, Andreas Dilger <adilger@sun.com> wrote:
> On Sep 17, 2009  14:55 -0700, Curt Wohlgemuth wrote:
>> This patch fixes a problem with handling nested calls to
>> ext4_journal_start/ext4_journal_stop, when there is no journal present.
>>
>>       Signed-off-by: Curt Wohlgemuth <curtw@google.com>
>> ---
>>
>> Instead of using the special value of
>>
>>         (handle_t *)0x1
>>
>> to represent a handle when there is no journal present, we now use a real
>> handle_t, so we can use its ref counting.  The h_transaction field now
>> determines if there is a journal present or not.
>
> You _could_ just use the "handle" value as a refcount, and anything less
> than, say, 4096 is considered a "special" handle.  I can't imagine the
> refcount being more than 3 or 4 even in extreme cases.

That's an elegant idea; thanks.  I'll work this up and send a patch out for it.

Thanks,
Curt

>
> Cheers, Andreas
> --
> Andreas Dilger
> Sr. Staff Engineer, Lustre Group
> Sun Microsystems of Canada, Inc.
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-09-18 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 21:55 [PATCH 2/2] ext4: Handle nested ext4_journal_start/stop calls without a journal Curt Wohlgemuth
2009-09-18  5:50 ` Andreas Dilger
2009-09-18 18:33   ` Curt Wohlgemuth [this message]
2009-09-18 21:33     ` Curt Wohlgemuth
2009-09-23 14:39       ` Curt Wohlgemuth

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=6601abe90909181133g27458301nb3aae756e473541c@mail.gmail.com \
    --to=curtw@google.com \
    --cc=adilger@sun.com \
    --cc=linux-ext4@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).