From: Andrea Arcangeli <andrea@suse.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Greg KH <greg@kroah.com>,
Andrew Morton <akpm@osdl.org>,
dipankar@in.ibm.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
paulmck@us.ibm.com
Subject: Re: [PATCH] RCU: Reduce size of rcu_head 1 of 2
Date: Mon, 18 Aug 2003 16:16:06 +0200 [thread overview]
Message-ID: <20030818141606.GU7862@dualathlon.random> (raw)
In-Reply-To: <20030808193441.56F452C25E@lists.samba.org>
Hi,
On Fri, Aug 08, 2003 at 12:21:04PM +1000, Rusty Russell wrote:
> There are two patches. Both reduce the size of the "struct rcu_head".
> One simply changes the struct rcu_head from a double linked list to a
> single linked list. The other eliminates the "void *data" arg, and
> changes the prototype of the call_rcu() function to take a pointer to
> the struct rcu_head, rather than a user-defined data ptr.
>
> It is the latter that I am concerned about changing mid-stable-series.
given the number of users (a dozen) I wouldn't be concerned about the
API change either. Much better to change it now that there arne't out of
the tree users yet. IMHO kernel internal API changes aren't a problem if
there are few users all in tree like in this case.
Andrea
next prev parent reply other threads:[~2003-08-18 17:17 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 [this message]
2003-08-25 3:35 ` Rusty Russell
2003-08-02 1:16 ` Mitchell Blank Jr
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=20030818141606.GU7862@dualathlon.random \
--to=andrea@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dipankar@in.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--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