All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [Patch] Constrain DMADOM/swiotlb allocations to 1G phys to fix b44 NIC driver
Date: Tue, 28 Nov 2006 16:31:33 +0000	[thread overview]
Message-ID: <20061128163133.103d7b4f@localhost.localdomain> (raw)
In-Reply-To: <1164728964.10380.19.camel@sisko.scot.redhat.com>

> > constraint for the DMADOM heap; and changes the x86/x86_64 swiotlb to
> > request a 30-bit constraint for allocations of the swiotlb memory.

(The hardware pseudo-iommu on the AMD can't handle this either as it can
only appear in the PCI window)

> The 30 bit constraint is enough to let b44 work.  But there are a number
> of sound cards which require a 28-bit DMA mask (256MB max physical
> addressable memory).  1GB seems reasonably safe, but I'm much less
> comfortable with restricting DMADOM to 256MB by default.  Does anyone
> have any strong feelings about shifting this?  What other users of
> DMADOM are there that might overflow if we restrict it even further?

For modern hardware the constraints are primarily the 30/31bit ones found
on some devices that know too much about Windows. The older sound cards
with 28bit limits like the ESS Maestro series are very much "old tech"
now. 

Alan

  parent reply	other threads:[~2006-11-28 16:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28 15:46 [Patch] Constrain DMADOM/swiotlb allocations to 1G phys to fix b44 NIC driver Stephen C. Tweedie
2006-11-28 15:49 ` Stephen C. Tweedie
2006-11-28 16:01   ` Keir Fraser
2006-11-28 16:31   ` Alan [this message]
2006-11-28 16:29     ` Muli Ben-Yehuda
2006-11-29  0:26       ` Re: [Patch] Constrain DMADOM/swiotlb allocations to1G " Ian Pratt
2006-11-28 16:33     ` Re: [Patch] Constrain DMADOM/swiotlb allocations to 1G " Keir Fraser
2006-11-28 15:54 ` Keir Fraser
2006-11-28 16:28   ` Alan

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=20061128163133.103d7b4f@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=sct@redhat.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.