public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: tek-life <teklife.kernel@gmail.com>,
	dhazelton@enter.net, oliver@neukum.org,
	linux-kernel@vger.kernel.org
Subject: Re: Can we remove the Zone_DMA?
Date: Mon, 12 Apr 2010 10:41:00 +0200	[thread overview]
Message-ID: <871velawrn.fsf@basil.nowhere.org> (raw)
In-Reply-To: <m18w93hati.fsf@fess.ebiederm.org> (Eric W. Biederman's message of "Sun, 04 Apr 2010 01:38:17 -0700")

ebiederm@xmission.com (Eric W. Biederman) writes:

Revisiting old posts. Sorry for digging up this old thread
from its grave.

> Ultimately I don't see much point in disabling ZONE_DMA.  It is a lot of
> work to track down if it is really needed, and it only costs 16MB.  So
> unless someone shows me that ZONE_DMA triggers the OOM killer unnecessarily
> or otherwise impacts the system what does legacy code hurt?

It has quite a lot of impact on slab for example.

The main users today are mostly some users who need to have less tha 4GB
on 64bit systems. The problem is for those often 16MB is not enough.
So on many systems 16MB is too much and on others it isn't enough.

A long time ago I had a patchkit to replace it with a range allocator,
merge it with softiotlb and replace all the allocations with real masks.

It never got quite merged and still needed some more work.

ftp://firstfloor.org/pub/ak/dma/INTRO

All the issues described in the INTRO are still there.

-Andi
-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2010-04-12  8:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04  4:21 Can we remove the Zone_DMA? tek-life
2010-04-04  5:07 ` Daniel Hazelton
     [not found]   ` <k2tc58e39921004032226ze2eb64dev21f8c2d137a49ebc@mail.gmail.com>
2010-04-04  5:33     ` Fwd: " tek-life
2010-04-04  7:49       ` Daniel Hazelton
2010-04-04  8:16         ` Thomas Fjellstrom
2010-04-04  8:28         ` tek-life
2010-04-04  8:28         ` tek-life
2010-04-04  8:38           ` Eric W. Biederman
2010-04-12  8:41             ` Andi Kleen [this message]
2010-04-18 11:04   ` Bernd Petrovitsch
2010-04-19 13:44     ` Lennart Sorensen
2010-04-04  7:31 ` Oliver Neukum
2010-04-04  9:07 ` Joerg Roedel

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=871velawrn.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=dhazelton@enter.net \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=teklife.kernel@gmail.com \
    /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