Re: [PATCH net-next V1 09/10] net/mlx5: Fix global UAR mapping

2016-02-29 Thread Saeed Mahameed
> > Well anyone can see that from the code. > > You have to explain why. In a simple words as partially explained in the commit message we want to have both mappings (NC and WC) available so upper layer can decide which to choose e.g. for SQs/QPs in some cases (Small Packets) and only when WC is s

Re: [PATCH net-next V1 09/10] net/mlx5: Fix global UAR mapping

2016-02-28 Thread David Miller
From: Saeed Mahameed Date: Sun, 28 Feb 2016 17:09:10 +0200 > We use ARCH_HAS_IOREMAP_WC to know if the current arch supports WC > (Write combining) IO memory mapping, if it is not supported > "uar->bf_map" will be NULL, thus we will use NC (Non Cached) mapping > "uar->map". This description suck

[PATCH net-next V1 09/10] net/mlx5: Fix global UAR mapping

2016-02-28 Thread Saeed Mahameed
From: Moshe Lazer Remove the global WC mapping of the total UARs since UAR mapping should be decided per UAR (e.g we want different mappings for EQs, CQs vs QPs). We use ARCH_HAS_IOREMAP_WC to know if the current arch supports WC (Write combining) IO memory mapping, if it is not supported "uar->