On Thu, Aug 17, 2017 at 2:17 PM, Jan Vesely wrote:
> Hi,
>
> thanks a lot for these answers.
>
> On Thu, 2017-08-17 at 15:01 +0200, Christian König wrote:
>> Am 17.08.2017 um 13:54 schrieb Jan Vesely:
>> > On Thu, 2017-08-17 at 11:54 +0200, Christian König wrote:
>> > >
Hi,
thanks a lot for these answers.
On Thu, 2017-08-17 at 15:01 +0200, Christian König wrote:
> Am 17.08.2017 um 13:54 schrieb Jan Vesely:
> > On Thu, 2017-08-17 at 11:54 +0200, Christian König wrote:
> > > [SNIP]
> > > In general ATS works completely different to GPUVM and is rather bound
> > >
Am 17.08.2017 um 13:54 schrieb Jan Vesely:
On Thu, 2017-08-17 at 11:54 +0200, Christian König wrote:
[SNIP]
In general ATS works completely different to GPUVM and is rather bound
to the CPU page tables.
But GPUVM on everything before Vega10 has a so called fragmentation size
in their page
On Thu, 2017-08-17 at 11:54 +0200, Christian König wrote:
> Am 17.08.2017 um 06:30 schrieb Jan Vesely:
> > On Wed, 2017-08-16 at 23:49 -0400, Alex Deucher wrote:
> > > On Wed, Aug 16, 2017 at 11:34 PM, Michel Dänzer
> > > wrote:
> > > > On 17/08/17 12:33 PM, Aaron Watry
Am 17.08.2017 um 06:30 schrieb Jan Vesely:
On Wed, 2017-08-16 at 23:49 -0400, Alex Deucher wrote:
On Wed, Aug 16, 2017 at 11:34 PM, Michel Dänzer wrote:
On 17/08/17 12:33 PM, Aaron Watry wrote:
On Wed, Aug 16, 2017 at 9:48 PM, Alex Deucher wrote:
On Wed, 2017-08-16 at 23:49 -0400, Alex Deucher wrote:
> On Wed, Aug 16, 2017 at 11:34 PM, Michel Dänzer wrote:
> > On 17/08/17 12:33 PM, Aaron Watry wrote:
> > > On Wed, Aug 16, 2017 at 9:48 PM, Alex Deucher
> > > wrote:
> > > > On Wed, Aug 16, 2017
On Wed, Aug 16, 2017 at 11:34 PM, Michel Dänzer wrote:
> On 17/08/17 12:33 PM, Aaron Watry wrote:
>> On Wed, Aug 16, 2017 at 9:48 PM, Alex Deucher wrote:
>>> On Wed, Aug 16, 2017 at 10:39 PM, Michel Dänzer wrote:
On 17/08/17
On 17/08/17 12:33 PM, Aaron Watry wrote:
> On Wed, Aug 16, 2017 at 9:48 PM, Alex Deucher wrote:
>> On Wed, Aug 16, 2017 at 10:39 PM, Michel Dänzer wrote:
>>> On 17/08/17 10:52 AM, Aaron Watry wrote:
PIPE_CAP_RESOURCE_FROM_USER_MEMORY says that size
On Wed, Aug 16, 2017 at 9:48 PM, Alex Deucher wrote:
> On Wed, Aug 16, 2017 at 10:39 PM, Michel Dänzer wrote:
>> On 17/08/17 10:52 AM, Aaron Watry wrote:
>>> PIPE_CAP_RESOURCE_FROM_USER_MEMORY says that size must be page aligned,
>>> but doesn't
On 17/08/17 11:48 AM, Alex Deucher wrote:
> On Wed, Aug 16, 2017 at 10:39 PM, Michel Dänzer wrote:
>> On 17/08/17 10:52 AM, Aaron Watry wrote:
>>> PIPE_CAP_RESOURCE_FROM_USER_MEMORY says that size must be page aligned,
>>> but doesn't necessarily say anything about the size of
On Wed, Aug 16, 2017 at 10:39 PM, Michel Dänzer wrote:
> On 17/08/17 10:52 AM, Aaron Watry wrote:
>> PIPE_CAP_RESOURCE_FROM_USER_MEMORY says that size must be page aligned,
>> but doesn't necessarily say anything about the size of those pages.
>
> Is there any case known so
On 17/08/17 10:52 AM, Aaron Watry wrote:
> PIPE_CAP_RESOURCE_FROM_USER_MEMORY says that size must be page aligned,
> but doesn't necessarily say anything about the size of those pages.
Is there any case known so far where it's not the CPU page size?
--
Earthling Michel Dänzer |
12 matches
Mail list logo