Re: [RFC PATCH 1/7] swiotlb: Instead of tracking the end of the swiotlb region just calculate it

2012-10-04 Thread Konrad Rzeszutek Wilk
On Thu, Oct 04, 2012 at 08:54:09AM -0700, Alexander Duyck wrote: > On 10/04/2012 06:01 AM, Konrad Rzeszutek Wilk wrote: > > On Wed, Oct 03, 2012 at 05:38:47PM -0700, Alexander Duyck wrote: > >> In the case of swiotlb we already have the start of the region and the > >> number > >> of slabs that

Re: [RFC PATCH 1/7] swiotlb: Instead of tracking the end of the swiotlb region just calculate it

2012-10-04 Thread Alexander Duyck
On 10/04/2012 06:01 AM, Konrad Rzeszutek Wilk wrote: > On Wed, Oct 03, 2012 at 05:38:47PM -0700, Alexander Duyck wrote: >> In the case of swiotlb we already have the start of the region and the number >> of slabs that give us the region size. Instead of having to call >> virt_to_phys on two

Re: [RFC PATCH 1/7] swiotlb: Instead of tracking the end of the swiotlb region just calculate it

2012-10-04 Thread Konrad Rzeszutek Wilk
On Wed, Oct 03, 2012 at 05:38:47PM -0700, Alexander Duyck wrote: > In the case of swiotlb we already have the start of the region and the number > of slabs that give us the region size. Instead of having to call > virt_to_phys on two pointers we can just take advantage of the fact that the >

Re: [RFC PATCH 1/7] swiotlb: Instead of tracking the end of the swiotlb region just calculate it

2012-10-04 Thread Konrad Rzeszutek Wilk
On Wed, Oct 03, 2012 at 05:38:47PM -0700, Alexander Duyck wrote: In the case of swiotlb we already have the start of the region and the number of slabs that give us the region size. Instead of having to call virt_to_phys on two pointers we can just take advantage of the fact that the region

Re: [RFC PATCH 1/7] swiotlb: Instead of tracking the end of the swiotlb region just calculate it

2012-10-04 Thread Alexander Duyck
On 10/04/2012 06:01 AM, Konrad Rzeszutek Wilk wrote: On Wed, Oct 03, 2012 at 05:38:47PM -0700, Alexander Duyck wrote: In the case of swiotlb we already have the start of the region and the number of slabs that give us the region size. Instead of having to call virt_to_phys on two pointers we

Re: [RFC PATCH 1/7] swiotlb: Instead of tracking the end of the swiotlb region just calculate it

2012-10-04 Thread Konrad Rzeszutek Wilk
On Thu, Oct 04, 2012 at 08:54:09AM -0700, Alexander Duyck wrote: On 10/04/2012 06:01 AM, Konrad Rzeszutek Wilk wrote: On Wed, Oct 03, 2012 at 05:38:47PM -0700, Alexander Duyck wrote: In the case of swiotlb we already have the start of the region and the number of slabs that give us the

[RFC PATCH 1/7] swiotlb: Instead of tracking the end of the swiotlb region just calculate it

2012-10-03 Thread Alexander Duyck
In the case of swiotlb we already have the start of the region and the number of slabs that give us the region size. Instead of having to call virt_to_phys on two pointers we can just take advantage of the fact that the region is linear and just compute the end based on the start plus the size.

[RFC PATCH 1/7] swiotlb: Instead of tracking the end of the swiotlb region just calculate it

2012-10-03 Thread Alexander Duyck
In the case of swiotlb we already have the start of the region and the number of slabs that give us the region size. Instead of having to call virt_to_phys on two pointers we can just take advantage of the fact that the region is linear and just compute the end based on the start plus the size.