linux-kernel - Re: [RFC][PATCH 00/26] sched/numa

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F686163.40509@redhat.com>
Date:	Tue, 20 Mar 2012 12:52:19 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, Paul Turner <pjt@...gle.com>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Mike Galbraith <efault@....de>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Dan Smith <danms@...ibm.com>,
	Bharata B Rao <bharata.rao@...il.com>,
	Lee Schermerhorn <Lee.Schermerhorn@...com>,
	Andrea Arcangeli <aarcange@...hat.com>,
	Rik van Riel <riel@...hat.com>,
	Johannes Weiner <hannes@...xchg.org>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [RFC][PATCH 00/26] sched/numa

On 03/20/2012 12:48 PM, Peter Zijlstra wrote:
> On Tue, 2012-03-20 at 12:18 +0200, Avi Kivity wrote:
> > On 03/19/2012 10:03 PM, Peter Zijlstra wrote:
> > > On Mon, 2012-03-19 at 14:16 +0200, Avi Kivity wrote:
> > > > > Afaik we do not use dma engines for memory migration. 
> > > > 
> > > > We don't, but I think we should. 
> > >
> > > ISTR we (the community) had this discussion once. I also seem to
> > > remember the general consensus being that DMA engines would mostly
> > > likely not be worth the effort, although I can't really recall the
> > > specifics.
> > >
> > > Esp. for 4k pages the setup of the offload will likely be more expensive
> > > than actually doing the memcpy.
> > 
> > If you're copying a page, yes.  If you're copying a large vma, the
> > per-page setup cost is likely to be very low.
> > 
> > Especially if you're copying across nodes.
>
> But wouldn't you then have to wait for the entire copy to complete
> before accessing any of the memory? That sounds like a way worse latency
> hit than the per-page lazy-migrate.

You use the dma engine for eager copying, not on demand.

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/