mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: tek-life <teklife.kernel@gmail.com>
To: dhazelton@enter.net
Cc: linux-kernel@vger.kernel.org, ebiederm@xmission.com
Subject: Fwd: Can we remove the Zone_DMA?
Date: Sun, 4 Apr 2010 13:33:09 +0800	[thread overview]
Message-ID: <s2mc58e39921004032233rfd47a83eoa86b37ffe59d2e7@mail.gmail.com> (raw)
In-Reply-To: <k2tc58e39921004032226ze2eb64dev21f8c2d137a49ebc@mail.gmail.com>

Thanks for your reply.And do you means that , If I use a modern PC,such as
my pc (CPU:Intel dual-core 2.6GHZ; Memory 2GB; And no pci ).I can remove the
ZONE_DMA .And make sure this system also run smoothly as before?

在 2010年4月4日 下午1:07,Daniel Hazelton <dhazelton@enter.net>写道:

On Sunday 04 April 2010 12:21:54 am tek-life wrote:
> > I’m a newbie on the linux kernel. Now I am reading the source code of
> > Linux . I have a question in the following about ZONE_DMA.
> >
> >
> > In Linux , The Memory is divided to three zone. They are ZONE_DMA
> > 、ZONE_NORMAL  and ZONE_HIGHMEM. From the book of "Undstand the Linux
> > kernel ", the ZONE_DMA has the effect that the Direct Memory Access
> > (DMA) processors for old ISA buses have a strong limitation: they are
> > able to address only the first 16 MB of RAM. SO ,we must set a zone
> > for  the DMA on ISA bus.  And I suspect that the hardware has
> > developed so quickly .And  in this days the ISA has been weeded out.
> > And so ,if we not defined the ZONE_DMA, is the system be effected? And
> > why not remove ZONE_DMA from the kernel . If it cann‘t to do so,the
> > compatibility is the only reason?
>
> While ISA is gone as a true peripheral interconnect for new systems it
> does,
> actually, still live on in a lot of systems that Linux still supports.
> While
> those systems, generally, are running the same kernel and userspace they
> were
> a decade ago I have no doubt that somebody might find an old machine and
> put
> Linux on it - just because they could.
>
> And that also discounts the non-IBM PC machines that are out there that
> Linux
> also supports. While I don't know enough about them to say for sure, I am
> quite certain that at least some of them are still using the ISA bus.
>
> DRH
>



-- 
Laboratory of Service Computing Technology and System

p-web:http://tek-life.org/blog
QQ:150439216



-- 
Laboratory of Service Computing Technology and System

p-web:http://tek-life.org/blog
QQ:150439216

  parent reply	other threads:[~2010-04-04  5:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04  4:21 tek-life
2010-04-04  5:07 ` Daniel Hazelton
     [not found]   ` <k2tc58e39921004032226ze2eb64dev21f8c2d137a49ebc@mail.gmail.com>
2010-04-04  5:33     ` tek-life [this message]
2010-04-04  7:49       ` Fwd: " 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
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=s2mc58e39921004032233rfd47a83eoa86b37ffe59d2e7@mail.gmail.com \
    --to=teklife.kernel@gmail.com \
    --cc=dhazelton@enter.net \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®