All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	x86@kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	cpw@sgi.com
Subject: Re: #tj-percpu has been rebased
Date: Thu, 12 Feb 2009 12:44:08 +0900	[thread overview]
Message-ID: <49939B08.1050801@kernel.org> (raw)
In-Reply-To: <49939964.4070607@kernel.org>

Tejun Heo wrote:
> Hello,
> 
> Tejun Heo wrote:
>> Rusty Russell wrote:
>>> On Saturday 31 January 2009 16:16:59 Tejun Heo wrote:
>>>> Anyways, please pull from
>>>>
>>>>   git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git tj-percpu
>>> Thanks.  cpualloc patches rebased on top of it (I had to include the module
>>> patch I've got queued for 2.6.29, otherwise gratuitous conflicts):
>>>
>>> 	git://git.kernel.org/pub/scm/linux/kernel/git/rusty/tj-percpu-cpualloc master
>>>
>>> Boot tested here, but that's no guarantee that something didn't break.
>>>
>>> I'm going to be occupied with finishing off cpumask_t this cycle, so I'd be
>>> happy for you to take ownership of any and all of these that you want to keep.
>>> I'll try to keep up with other patches as you post them.
>> Will merge it in this week.
> 
> Okay, just went through the patchset.  It generally looks nice and
> clean but I'm still a bit hung up on the idea of making percpu area
> resizable.  I'll look into Christoph Lameter's cpu_alloc patchset too
> and think about it more.

Oops, those are the same ones.  I'll give a shot at cooking up
something which can be dynamically sized before going forward with
this one.

Thanks.

-- 
tejun

  reply	other threads:[~2009-02-12  3:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 17:05 #tj-percpu has been rebased Tejun Heo
2009-01-31  5:46 ` Tejun Heo
2009-01-31 13:28   ` Ingo Molnar
2009-02-02  9:04   ` Rusty Russell
2009-02-04  3:18     ` Tejun Heo
2009-02-12  3:37       ` Tejun Heo
2009-02-12  3:44         ` Tejun Heo [this message]
2009-02-13 20:58           ` Rusty Russell
2009-02-13 21:17             ` Jeremy Fitzhardinge
2009-02-13 22:59             ` H. Peter Anvin
2009-02-14  0:45             ` Tejun Heo
2009-02-14  1:53               ` H. Peter Anvin
2009-02-14  2:10                 ` Tejun Heo
2009-02-16  7:23               ` Rusty Russell
2009-02-16 17:28                 ` H. Peter Anvin
2009-02-16 23:22                   ` Rusty Russell
2009-02-16 23:28                     ` H. Peter Anvin
2009-02-18  4:25                       ` Rusty Russell
2009-02-18  6:40                         ` H. Peter Anvin
2009-02-18  7:11                           ` Rusty Russell

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=49939B08.1050801@kernel.org \
    --to=tj@kernel.org \
    --cc=cpw@sgi.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.