linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [PATCH] PCIE: pcie_set_readrq must not be allowed by PCIE EP driver
       [not found]         ` <4D806132.1090704@st.com>
@ 2012-02-23 10:01           ` Pratyush Anand
  2012-02-23 17:42             ` Tejun Heo
  0 siblings, 1 reply; 5+ messages in thread
From: Pratyush Anand @ 2012-02-23 10:01 UTC (permalink / raw)
  To: tj
  Cc: Pedanekar, Hemant, linux-pci@vger.kernel.org, Viresh KUMAR,
	Shiraz HASHIM, Armando VISCONTI, Vipin KUMAR, Deepak SIKRI,
	Rajeev KUMAR, Vipul Kumar SAMAR, Amit VIRDI, Bhupesh SHARMA

Hi Tejun,

Its a long pending patch.
Any decision on this patch.

Regards
Pratyush

On 3/16/2011 12:35 PM, pratyush wrote:
> Hello Hemant,
>
> On 3/16/2011 9:43 AM, Pedanekar, Hemant wrote:
>>> What happens in your case? Does it not work, if you do not
>>>> modify sil driver?
>>>>
>> I also require to modify the sil driver to avoid setting max RRQ to 4096
>> otherwise the data transfer over PCIe does not work. The RC responds with
>> "Unsupported Request" for read request of size greater than 256 bytes.
>>
>> The other problem is, there is no way for peers to know that the other
>> device cannot handle RRQ of size beyond certain limit. At least I am not
>> aware of any bits in PCIe configuration space which advertise this. Do you
>> know of any such?
>>
>> While, there is "Max RRQ size" field in device control register which only
>> controls outbound RRQ size.
>>
>> This restriction probbaly will complicate more when the device with such
>> RRQ limitation is a EP, in such case, no one else than the EP (and its driver)
>> would know about this limitation and need to force others (including RC) to
>> reduce the max RRQ size.
>>
>
> Yes, I am agreed with you. I do not see any way to inform its peers about request
> limit. So I think that a EP driver should not be allowed to call any function which
> changes EP's RRQ size. It should always be RC driver which sets these values as
> per max capability of the link.
>
> Currently I am managing it with postinit hook of RC driver. But can be part of
> common pci stack.
>
> You can see my way of handling it at
> http://www.spinics.net/lists/linux-pci/msg09897.html
>
> Regards
> Pratyush


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] PCIE: pcie_set_readrq must not be allowed by PCIE EP driver
  2012-02-23 10:01           ` [PATCH] PCIE: pcie_set_readrq must not be allowed by PCIE EP driver Pratyush Anand
@ 2012-02-23 17:42             ` Tejun Heo
  2012-02-24  3:57               ` Pratyush Anand
  0 siblings, 1 reply; 5+ messages in thread
From: Tejun Heo @ 2012-02-23 17:42 UTC (permalink / raw)
  To: Pratyush Anand
  Cc: Pedanekar, Hemant, linux-pci@vger.kernel.org, Viresh KUMAR,
	Shiraz HASHIM, Armando VISCONTI, Vipin KUMAR, Deepak SIKRI,
	Rajeev KUMAR, Vipul Kumar SAMAR, Amit VIRDI, Bhupesh SHARMA

Hello,

On Thu, Feb 23, 2012 at 03:31:29PM +0530, Pratyush Anand wrote:
> Its a long pending patch.
> Any decision on this patch.

Hmmm.... I really don't know what to do.  IIRC it was something lifted
from the proprietary sil driver and they probably added that to work
around performance oddities under certain configurations and I'm a bit
worried about changing it after all this time.  Is there any way to
make this conditional somehow?

Thanks.

-- 
tejun

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] PCIE: pcie_set_readrq must not be allowed by PCIE EP driver
  2012-02-23 17:42             ` Tejun Heo
@ 2012-02-24  3:57               ` Pratyush Anand
  2012-02-24  5:38                 ` Pedanekar, Hemant
  0 siblings, 1 reply; 5+ messages in thread
From: Pratyush Anand @ 2012-02-24  3:57 UTC (permalink / raw)
  To: Tejun Heo
  Cc: Pedanekar, Hemant, linux-pci@vger.kernel.org, Viresh KUMAR,
	Shiraz HASHIM, Armando VISCONTI, Vipin KUMAR, Deepak SIKRI,
	Rajeev KUMAR, Vipul Kumar SAMAR, Amit VIRDI, Bhupesh SHARMA

On 2/23/2012 11:12 PM, Tejun Heo wrote:
> Hello,
>
> On Thu, Feb 23, 2012 at 03:31:29PM +0530, Pratyush Anand wrote:
>> Its a long pending patch.
>> Any decision on this patch.
>
> Hmmm.... I really don't know what to do.  IIRC it was something lifted
> from the proprietary sil driver and they probably added that to work
> around performance oddities under certain configurations and I'm a bit
> worried about changing it after all this time.  Is there any way to
> make this conditional somehow?

I see that there is a patch in the latest kernel.

commit a1c473aa11e61bc871be16279c9bf976acf22504
Author: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date:   Fri Oct 14 14:56:15 2011 -0500

     pci: Clamp pcie_set_readrq() when using "performance" settings

I think, this will resolve the issue.
We are moving to the new kernel. Will check it there.

Regards
Pratyush

>
> Thanks.
>


^ permalink raw reply	[flat|nested] 5+ messages in thread

* RE: [PATCH] PCIE: pcie_set_readrq must not be allowed by PCIE EP driver
  2012-02-24  3:57               ` Pratyush Anand
@ 2012-02-24  5:38                 ` Pedanekar, Hemant
  2012-02-24  6:09                   ` Pratyush Anand
  0 siblings, 1 reply; 5+ messages in thread
From: Pedanekar, Hemant @ 2012-02-24  5:38 UTC (permalink / raw)
  To: Pratyush Anand, Tejun Heo
  Cc: linux-pci@vger.kernel.org, Viresh KUMAR, Shiraz HASHIM,
	Armando VISCONTI, Vipin KUMAR, Deepak SIKRI, Rajeev KUMAR,
	Vipul Kumar SAMAR, Amit VIRDI, Bhupesh SHARMA

Hi,

Pratyush Anand wrote on Friday, February 24, 2012 9:28 AM:

> On 2/23/2012 11:12 PM, Tejun Heo wrote:
>> Hello,
>> 
>> On Thu, Feb 23, 2012 at 03:31:29PM +0530, Pratyush Anand wrote:
>>> Its a long pending patch.
>>> Any decision on this patch.
>> 
>> Hmmm.... I really don't know what to do.  IIRC it was something lifted
>> from the proprietary sil driver and they probably added that to work
>> around performance oddities under certain configurations and I'm a bit
>> worried about changing it after all this time.  Is there any way to
>> make this conditional somehow?
> 
> I see that there is a patch in the latest kernel.
> 
> commit a1c473aa11e61bc871be16279c9bf976acf22504
> Author: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Date:   Fri Oct 14 14:56:15 2011 -0500
> 
>      pci: Clamp pcie_set_readrq() when using "performance" settings
> 
> I think, this will resolve the issue.
> We are moving to the new kernel. Will check it there.
> 
I see that the patch above considers MPS to clamp RRQ size, while I think
both should be independent, or perhaps I am missing something. 

Not allowing EP drivers to choose max RRQ setting for their respective 
devices will prevent breaking the mismatches where EP sends RRQ which RC 
cannot handle.

Other option is that the EP drivers which force max RRQ size also handle
the case where they get completor abort (or it wil be UR?) from the 
completor and then try to use lower (or lowest) read request. This will 
prevent breaking the data paths at the same time allowing systems which are
capable to have max performance.

Thanks.

   Hemant

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] PCIE: pcie_set_readrq must not be allowed by PCIE EP driver
  2012-02-24  5:38                 ` Pedanekar, Hemant
@ 2012-02-24  6:09                   ` Pratyush Anand
  0 siblings, 0 replies; 5+ messages in thread
From: Pratyush Anand @ 2012-02-24  6:09 UTC (permalink / raw)
  To: Pedanekar, Hemant
  Cc: Tejun Heo, linux-pci@vger.kernel.org, Viresh KUMAR, Shiraz HASHIM,
	Armando VISCONTI, Vipin KUMAR, Deepak SIKRI, Rajeev KUMAR,
	Vipul Kumar SAMAR, Amit VIRDI, Bhupesh SHARMA

On 2/24/2012 11:08 AM, Pedanekar, Hemant wrote:
> Hi,
>
> Pratyush Anand wrote on Friday, February 24, 2012 9:28 AM:
>
>> On 2/23/2012 11:12 PM, Tejun Heo wrote:
>>> Hello,
>>>
>>> On Thu, Feb 23, 2012 at 03:31:29PM +0530, Pratyush Anand wrote:
>>>> Its a long pending patch.
>>>> Any decision on this patch.
>>>
>>> Hmmm.... I really don't know what to do.  IIRC it was something lifted
>>> from the proprietary sil driver and they probably added that to work
>>> around performance oddities under certain configurations and I'm a bit
>>> worried about changing it after all this time.  Is there any way to
>>> make this conditional somehow?
>>
>> I see that there is a patch in the latest kernel.
>>
>> commit a1c473aa11e61bc871be16279c9bf976acf22504
>> Author: Benjamin Herrenschmidt<benh@kernel.crashing.org>
>> Date:   Fri Oct 14 14:56:15 2011 -0500
>>
>>       pci: Clamp pcie_set_readrq() when using "performance" settings
>>
>> I think, this will resolve the issue.
>> We are moving to the new kernel. Will check it there.
>>
> I see that the patch above considers MPS to clamp RRQ size, while I think
> both should be independent, or perhaps I am missing something.
>

Please also see following patch for completeness.

commit b03e7495a862b028294f59fc87286d6d78ee7fa1
Author: Jon Mason <mason@myri.com>
Date:   Wed Jul 20 15:20:54 2011 -0500

     PCI: Set PCI-E Max Payload Size on fabric

Regards
Pratyush

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2012-02-24  6:09 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <1297937650-2558-1-git-send-email-pratyush.anand@st.com>
     [not found] ` <2A3DCF3DA181AD40BDE86A3150B27B6B0373799132@dbde02.ent.ti.com>
     [not found]   ` <2A3DCF3DA181AD40BDE86A3150B27B6B03737991EA@dbde02.ent.ti.com>
     [not found]     ` <4D78D6E3.50004@st.com>
     [not found]       ` <2A3DCF3DA181AD40BDE86A3150B27B6B03743048FE@dbde02.ent.ti.com>
     [not found]         ` <4D806132.1090704@st.com>
2012-02-23 10:01           ` [PATCH] PCIE: pcie_set_readrq must not be allowed by PCIE EP driver Pratyush Anand
2012-02-23 17:42             ` Tejun Heo
2012-02-24  3:57               ` Pratyush Anand
2012-02-24  5:38                 ` Pedanekar, Hemant
2012-02-24  6:09                   ` Pratyush Anand

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).