From: Mitchell Blank Jr <mitch@sfgoth.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RCU: Reduce size of rcu_head 1 of 2
Date: Fri, 1 Aug 2003 18:16:44 -0700 [thread overview]
Message-ID: <20030802011644.GG33201@gaz.sfgoth.com> (raw)
In-Reply-To: <20030801160036.029e542b.akpm@osdl.org>
Andrew Morton wrote:
> > Gratuitous change to API during stable series BAD BAD BAD. If
> > you drop this it stays as is until 2.8. The extra arg in
> > unneccessary, but breaking it is worse.
>
> There won't be any out-of-tree users by then.
I must be misunderstanding something. If the point of the patch is to
shrink "struct rcu_head" (which it seems to do) won't that change
offsets in all sorts of things like "struct dentry"? I know we
officially don't care about binary modules but a change like that
seems pretty gratuitous for such a small gain.
This sounds like the kind of change that should either happen now or
wait for 2.7.1 (and not be backported into 2.6)
-Mitch
next prev parent reply other threads:[~2003-08-02 1:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 18:58 [PATCH] RCU: Reduce size of rcu_head 1 of 2 Dipankar Sarma
2003-07-31 19:06 ` [PATCH] RCU: Reduce size of rcu_head 2 " Dipankar Sarma
2003-07-31 20:49 ` [PATCH] RCU: Reduce size of rcu_head 1 " Andrew Morton
2003-07-31 21:31 ` Dipankar Sarma
2003-07-31 21:25 ` Andrew Morton
2003-08-01 21:16 ` Rusty Russell
2003-08-01 23:00 ` Andrew Morton
2003-08-02 0:32 ` Rusty Russell
2003-08-02 1:19 ` Greg KH
2003-08-02 1:49 ` Rusty Russell
2003-08-02 13:15 ` Alan Cox
2003-08-08 2:21 ` Rusty Russell
2003-08-18 14:16 ` Andrea Arcangeli
2003-08-25 3:35 ` Rusty Russell
2003-08-02 1:16 ` Mitchell Blank Jr [this message]
2003-08-02 1:43 ` Matt Mackall
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=20030802011644.GG33201@gaz.sfgoth.com \
--to=mitch@sfgoth.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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