From: ebiederm@xmission.com (Eric W. Biederman)
To: tek-life <teklife.kernel@gmail.com>
Cc: dhazelton@enter.net, oliver@neukum.org, linux-kernel@vger.kernel.org
Subject: Re: Can we remove the Zone_DMA?
Date: Sun, 04 Apr 2010 01:38:17 -0700 [thread overview]
Message-ID: <m18w93hati.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <j2rc58e39921004040128xb502c314u4b6b080a77fee813@mail.gmail.com> (tek-life's message of "Sun\, 4 Apr 2010 16\:28\:49 +0800")
tek-life <teklife.kernel@gmail.com> writes:
> Thanks for your replys.
> I was confused. The motherboard of Intel i810 chipset in early 1999
> had not supported the ISA. You say keyboard should use ISA, what
> should work for the pc using the i810 motherboard. More important ,
> the keyboard don't use DMA.
Last I heard this discussed it was mentioned that there were some
fairly common integrated sound devices using ISA DMA.
As for the i810 chipset not supporting ISA that isn't really true. No
one implements ISA plug-in slots, but at least in the for of LPC
hardware that is effectively ISA continues to be supported for various
legacy devices.
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?
Eric
next prev parent reply other threads:[~2010-04-04 8:38 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 [this message]
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=m18w93hati.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=dhazelton@enter.net \
--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