From: Andrew Morton <akpm@osdl.org>
To: dipankar@in.ibm.com
Cc: rusty@rustcorp.com.au, andrea@suse.de,
linux-kernel@vger.kernel.org, paulmck@us.ibm.com
Subject: Re: [PATCH] RCU: Reduce size of rcu_head 1 of 2
Date: Thu, 31 Jul 2003 14:25:45 -0700 [thread overview]
Message-ID: <20030731142545.7bcb50fb.akpm@osdl.org> (raw)
In-Reply-To: <20030731213103.GB17709@in.ibm.com>
Dipankar Sarma <dipankar@in.ibm.com> wrote:
>
> The linked-list change is internal enough for a future backport from
> 2.7. The only concern here is the change in call_rcu() API. What would
> be a good way to manage that ?
Oh I'd be okay with merging a change like this into (say) 2.6.3-pre1,
without it having had a run in 2.7. We need to be able to do things like
that.
But right now we need to be fully focussed upon important features which
are late (cpumask_t, 64-bit dev_t, 4G+4G, etc) and upon stabilisation of the
current tree.
next prev parent reply other threads:[~2003-07-31 21:38 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 [this message]
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
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=20030731142545.7bcb50fb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=dipankar@in.ibm.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;
as well as URLs for NNTP newsgroup(s).