From: "Jan Beulich" <JBeulich@novell.com>
To: <mingo@elte.hu>, "FUJITA Tomonori" <fujita.tomonori@lab.ntt.co.jp>
Cc: <yinghai@kernel.org>, <tglx@linutronix.de>, <tiwai@suse.de>,
<linux-kernel@vger.kernel.org>, <jbarnes@virtuousgeek.org>,
<hpa@zytor.com>
Subject: Re: [PATCH] x86: adjust GFP mask handling for coherent allocations
Date: Tue, 27 Oct 2009 08:58:14 +0000 [thread overview]
Message-ID: <4AE6C436020000780001BF10@vpn.id2.novell.com> (raw)
In-Reply-To: <20091027103758L.fujita.tomonori@lab.ntt.co.jp>
>>> FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> 27.10.09 02:38 >>>
>On Mon, 26 Oct 2009 21:19:17 +0100
>Ingo Molnar <mingo@elte.hu> wrote:
>> Well, can ISA_BIT_MASK fall back to DMA_BIT_MASK(32) on !CONFIG_ISA? If
>> we have ISA support disabled we might as well pretend the whole world is
>> PCI, right?
>
>I don't think that it works. At least, you can't do that with
>the DMA_BIT_MASK(24) in arch/x86/kernl/pci-dma.c; it must be
>DMA_BIT_MASK(24) even with !CONFIG_ISA.
This one I too was about to point out, which is why I think
DMA_ISA_BIT_MASK should only be an alias of DMA_BIT_MASK(24), with
no fallback to DMA_BIT_MASK(32).
>> That way we'd get rid of that #ifdef in the .c code too.
>
>Well, in the first place, we don't need the #ifdef in Jan's patch. We
>can always use DMA_BIT_MASK(24) for the fallback device.
But this one I don't agree with - the purpose of the patch is to not have
a 24-bit (or 32-bit) mask here unconditionally: It would result in GFP_DMA
to be forced on for the allocation (which the patch specifically eliminates),
and for x86-64 this wasn't the case up to .25, which is the behavior I'm
trying to restore (and extend to the !CONFIG_ISA case for ix86).
Jan
next prev parent reply other threads:[~2009-10-27 8:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 12:03 Jan Beulich
2009-10-23 11:48 ` Ingo Molnar
2009-10-26 15:13 ` Jan Beulich
2009-10-26 15:22 ` Ingo Molnar
2009-10-26 15:45 ` Jan Beulich
2009-10-26 20:19 ` Ingo Molnar
2009-10-26 20:44 ` Jesse Barnes
2009-10-27 1:38 ` FUJITA Tomonori
2009-10-27 8:58 ` Jan Beulich [this message]
2009-10-27 9:00 ` Jan Beulich
2009-10-27 9:11 ` FUJITA Tomonori
2009-10-27 9:23 ` Jan Beulich
2009-10-27 9:37 ` FUJITA Tomonori
2009-10-27 9:47 ` Jan Beulich
2009-10-27 10:15 ` FUJITA Tomonori
2009-10-27 10:19 ` Alan Cox
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=4AE6C436020000780001BF10@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.de \
--cc=yinghai@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®