All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <tj@kernel.org>
Cc: Yinghai Lu <yinghai@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	David Rientjes <rientjes@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] x86, numa, emu: only transform numa_distance if SLIT is there
Date: Thu, 10 Mar 2011 09:55:33 +0100	[thread overview]
Message-ID: <20110310085533.GA25171@elte.hu> (raw)
In-Reply-To: <20110303062259.GI28266@mtj.dyndns.org>


* Tejun Heo <tj@kernel.org> wrote:

> On Wed, Mar 02, 2011 at 05:28:32PM -0800, Yinghai Lu wrote:
> > 
> > during copying should only copy with NEW numa_dist_cnt size.
> > need to call numa_alloc_dist() at first,  and it will set default values.
> > 
> > So we will not need to go over the big matrix without meaning.
> > 
> > Need to make numa_alloc_distance to return new numa_dist_cnt
> > 
> > Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> 
> I'm not taking this.  You can't send the same change twice and expect
> different result.

Ping: what's the status of this - Yinghai, are you working on an improved version of 
these (and related) patches, as per the review suggestions from Tejun - or are you 
dropping them?

Thanks,

	Ingo

  reply	other threads:[~2011-03-10  8:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03  1:25 [PATCH 1/2] x86, numa, emu: move size calculation into if block Yinghai Lu
2011-03-03  1:28 ` [PATCH 2/2] x86, numa, emu: only transform numa_distance if SLIT is there Yinghai Lu
2011-03-03  6:22   ` Tejun Heo
2011-03-10  8:55     ` Ingo Molnar [this message]
2011-03-03  6:21 ` [PATCH 1/2] x86, numa, emu: move size calculation into if block Tejun Heo

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=20110310085533.GA25171@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rientjes@google.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=yinghai@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.