From: Jambunathan K <jambunathan@netxen.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, sanjeev@netxen.com
Subject: Re: xen_create_contiguous_region - Regarding
Date: Fri, 06 Apr 2007 18:24:39 +0530 [thread overview]
Message-ID: <4616430F.2030507@netxen.com> (raw)
In-Reply-To: <C23BE869.580E%Keir.Fraser@cl.cam.ac.uk>
>> pci_map_single() will do what you want automatically. If you really want to
>> allocate contiguous memory yourself, allocate it then call
>> xen_create_contiguous_region().
Could you please export xen_create_contiguous_region for wider use?
Jambunathan K.
Keir Fraser wrote:
> On 6/4/07 11:46, "Jambunathan K" <jambunathan@netxen.com> wrote:
>
>> Given that we prefer to maintain our own bounce buffers, I could neither
>> find a dependable API that let the driver allocate machine contiguous
>> memory (that could later be *pci_map_singled*) nor find a suitable hook
>> to xen_create_contiguous_region.
>
> pci_map_single() will do what you want automatically. If you really want to
> allocate contiguous memory yourself, allocate it then call
> xen_create_contiguous_region().
>
>> As an aside, is there a tweak to "increase" contiguous memory regions
>> available so that xen_create_contiguous_regions() succeeds. On DomUs,
>> when swiotlb is enabled, I see some crashes which I would like to avoid
>> by redistributing memory resources.
>
> Xen will try to maintain contiguity as far as possible, but it cannot
> defragment the memory map.
>
> -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2007-04-06 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 10:46 xen_create_contiguous_region - Regarding Jambunathan K
2007-04-06 11:07 ` Keir Fraser
2007-04-06 12:54 ` Jambunathan K [this message]
2007-04-09 13:17 ` Jambunathan K
2007-04-09 13:24 ` Keir Fraser
2007-04-10 6:25 ` Jambunathan K
2007-04-10 9:17 ` Keir Fraser
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=4616430F.2030507@netxen.com \
--to=jambunathan@netxen.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=sanjeev@netxen.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.