public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Jani Monoses <jani@iv.ro>,
	linux-kernel@vger.kernel.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: [PATCH] 2.5.32 : u.ext3_sb -> generic_sbp
Date: Mon, 2 Sep 2002 13:30:26 +0100	[thread overview]
Message-ID: <20020902133026.A4105@redhat.com> (raw)
In-Reply-To: <3D6FC178.CC3E89CD@zip.com.au>; from akpm@zip.com.au on Fri, Aug 30, 2002 at 12:03:20PM -0700

Hi,

On Fri, Aug 30, 2002 at 12:03:20PM -0700, Andrew Morton wrote:

> > This turns the remaining parts of ext3 to EXT3_SB and turns the latter
> > from a macro to inline function which returns the generic_sbp field of u.
 
> It's not going to make the merge of all Stephen's 2.4 changes
> any more fun though ;)

For the major new changes in ext3, I think I'll end up bringing back a
lot of the 2.5 changes into a 2.4 branch.  Beyond a certain point,
though, I'll probably have to start basing new ext3 work on 2.5 ---
the BKL mitigation, in particular, is going to depend on the locking
regime which is substantially different in 2.5.  

My current codebase should help BKL in both 2.4 and 2.5 simply because
it substantially reduces the amount of work we're doing in the core,
without actually changing the locking, but eliminating BKL entirely in
larger chunks of the code will have to be the next stage.

--Stephen

      parent reply	other threads:[~2002-09-02 12:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-30 14:10 [PATCH] 2.5.32 : u.ext3_sb -> generic_sbp Jani Monoses
2002-08-30 19:03 ` Andrew Morton
2002-08-30 19:25   ` Andreas Dilger
2002-08-31 16:13   ` Dave Jones
2002-09-02 12:30     ` Stephen C. Tweedie
2002-09-02 12:30   ` Stephen C. Tweedie [this message]

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=20020902133026.A4105@redhat.com \
    --to=sct@redhat.com \
    --cc=akpm@zip.com.au \
    --cc=jani@iv.ro \
    --cc=linux-kernel@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