Hi Alex,
On 19/09/2017 18:58, Alex Williamson wrote:
> With virtual PCI-Express chipsets, we now see userspace/guest drivers
> trying to match the physical MPS setting to a virtual downstream port.
> Of course a lone physical device surrounded by virtual interconnects
> cannot make a correct
Hi Alex,
On 19/09/2017 18:58, Alex Williamson wrote:
> With virtual PCI-Express chipsets, we now see userspace/guest drivers
> trying to match the physical MPS setting to a virtual downstream port.
> Of course a lone physical device surrounded by virtual interconnects
> cannot make a correct
Hi Sinan,
On 20/09/2017 18:29, Sinan Kaya wrote:
> On 9/20/2017 12:11 PM, Alex Williamson wrote:
>> My impression is that the issue would be inefficiency. There should be
>> nothing functionally wrong with a read request less than MPS, but we're
>> not "filling" the TLP as much as the topology
Hi Sinan,
On 20/09/2017 18:29, Sinan Kaya wrote:
> On 9/20/2017 12:11 PM, Alex Williamson wrote:
>> My impression is that the issue would be inefficiency. There should be
>> nothing functionally wrong with a read request less than MPS, but we're
>> not "filling" the TLP as much as the topology
On 9/20/2017 12:11 PM, Alex Williamson wrote:
> My impression is that the issue would be inefficiency. There should be
> nothing functionally wrong with a read request less than MPS, but we're
> not "filling" the TLP as much as the topology allows. Is that your
> understanding as well, Sinan?
On 9/20/2017 12:11 PM, Alex Williamson wrote:
> My impression is that the issue would be inefficiency. There should be
> nothing functionally wrong with a read request less than MPS, but we're
> not "filling" the TLP as much as the topology allows. Is that your
> understanding as well, Sinan?
On Wed, 20 Sep 2017 16:26:25 +0200
Auger Eric wrote:
> Hi Sinan,
>
> On 20/09/2017 15:01, Sinan Kaya wrote:
> > On 9/20/2017 3:59 AM, Auger Eric wrote:
> >>> My impression is that MRRS is predominantly device and driver
> >>> dependent, not topology dependent. A device
On Wed, 20 Sep 2017 16:26:25 +0200
Auger Eric wrote:
> Hi Sinan,
>
> On 20/09/2017 15:01, Sinan Kaya wrote:
> > On 9/20/2017 3:59 AM, Auger Eric wrote:
> >>> My impression is that MRRS is predominantly device and driver
> >>> dependent, not topology dependent. A device can send a read
On 9/20/2017 10:26 AM, Auger Eric wrote:
>> Because completions are required to be a minimum of MPS size. If MRRS > MPS,
>> read response is sent as multiple completions.
> With that patch, you can end up with MRRS < MPS. Do I understand
> correctly this is an issue?
To give the right context, I
On 9/20/2017 10:26 AM, Auger Eric wrote:
>> Because completions are required to be a minimum of MPS size. If MRRS > MPS,
>> read response is sent as multiple completions.
> With that patch, you can end up with MRRS < MPS. Do I understand
> correctly this is an issue?
To give the right context, I
Hi Sinan,
On 20/09/2017 15:01, Sinan Kaya wrote:
> On 9/20/2017 3:59 AM, Auger Eric wrote:
>>> My impression is that MRRS is predominantly device and driver
>>> dependent, not topology dependent. A device can send a read request
>>> with a size larger than MPS, which implies that the device
Hi Sinan,
On 20/09/2017 15:01, Sinan Kaya wrote:
> On 9/20/2017 3:59 AM, Auger Eric wrote:
>>> My impression is that MRRS is predominantly device and driver
>>> dependent, not topology dependent. A device can send a read request
>>> with a size larger than MPS, which implies that the device
On 9/20/2017 9:01 AM, Sinan Kaya wrote:
> The only valid criteria is that MRRS needs to be a multiple of MPS.
>
> https://linuxplumbersconf.org/2017/ocw//system/presentations/4732/original/crs.pdf
>
Apologies for sending the wrong link. Correcting it.
On 9/20/2017 9:01 AM, Sinan Kaya wrote:
> The only valid criteria is that MRRS needs to be a multiple of MPS.
>
> https://linuxplumbersconf.org/2017/ocw//system/presentations/4732/original/crs.pdf
>
Apologies for sending the wrong link. Correcting it.
On 9/20/2017 3:59 AM, Auger Eric wrote:
>> My impression is that MRRS is predominantly device and driver
>> dependent, not topology dependent. A device can send a read request
>> with a size larger than MPS, which implies that the device supplying
>> the read data would split it into multiple
On 9/20/2017 3:59 AM, Auger Eric wrote:
>> My impression is that MRRS is predominantly device and driver
>> dependent, not topology dependent. A device can send a read request
>> with a size larger than MPS, which implies that the device supplying
>> the read data would split it into multiple
Hi Alex,
On 19/09/2017 22:20, Alex Williamson wrote:
> [cc +linux-pci, Sinan]
>
> On Tue, 19 Sep 2017 19:50:37 +0200
> Auger Eric wrote:
>
>> Hi Alex,
>>
>> On 19/09/2017 18:58, Alex Williamson wrote:
>>> With virtual PCI-Express chipsets, we now see userspace/guest
Hi Alex,
On 19/09/2017 22:20, Alex Williamson wrote:
> [cc +linux-pci, Sinan]
>
> On Tue, 19 Sep 2017 19:50:37 +0200
> Auger Eric wrote:
>
>> Hi Alex,
>>
>> On 19/09/2017 18:58, Alex Williamson wrote:
>>> With virtual PCI-Express chipsets, we now see userspace/guest drivers
>>> trying to match
[cc +linux-pci, Sinan]
On Tue, 19 Sep 2017 19:50:37 +0200
Auger Eric wrote:
> Hi Alex,
>
> On 19/09/2017 18:58, Alex Williamson wrote:
> > With virtual PCI-Express chipsets, we now see userspace/guest drivers
> > trying to match the physical MPS setting to a virtual
[cc +linux-pci, Sinan]
On Tue, 19 Sep 2017 19:50:37 +0200
Auger Eric wrote:
> Hi Alex,
>
> On 19/09/2017 18:58, Alex Williamson wrote:
> > With virtual PCI-Express chipsets, we now see userspace/guest drivers
> > trying to match the physical MPS setting to a virtual downstream port.
> > Of
Hi Alex,
On 19/09/2017 18:58, Alex Williamson wrote:
> With virtual PCI-Express chipsets, we now see userspace/guest drivers
> trying to match the physical MPS setting to a virtual downstream port.
> Of course a lone physical device surrounded by virtual interconnects
> cannot make a correct
Hi Alex,
On 19/09/2017 18:58, Alex Williamson wrote:
> With virtual PCI-Express chipsets, we now see userspace/guest drivers
> trying to match the physical MPS setting to a virtual downstream port.
> Of course a lone physical device surrounded by virtual interconnects
> cannot make a correct
22 matches
Mail list logo