From: Marin Mitov <mitov@issp.bas.bg>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: CONFIG_HIGHMEM or CONFIG_HIGHMEM64G in illegal_highdma()
Date: Wed, 7 May 2008 19:49:54 +0300 [thread overview]
Message-ID: <200805071949.54583.mitov@issp.bas.bg> (raw)
Hi all,
The usage of NETIF_F_HIGHDMA in drivers/net/* make me think its
purpose is to declare drivers's capability to address RAM above 4GB, OK?
For x86_64 CONFIG_HIGHMEM is not defined, so the function
illegal_highdma() found in net/core/dev.c returns 0 because
x86_64 has IOMMU mapping all RAM.
For x86_32 CONFIG_HIGHMEM is defined as
(CONFIG_HIGHMEM4G || CONFIG_HIGHMEM64G)
While CONFIG_HIGHMEM4G insures RAM is bellow 4GB some checks
are unnecessarily done.
Should we have CONFIG_HIGHMEM64G in illegal_highdma()
instead of CONFIG_HIGHMEM? If so should I post a patch?
Regards.
Marin Mitov
P.S. This is a resend, due to recent problems with http://lkml.org/
next reply other threads:[~2008-05-07 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 16:49 Marin Mitov [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-06 12:35 Marin Mitov
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=200805071949.54583.mitov@issp.bas.bg \
--to=mitov@issp.bas.bg \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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®