09/08/2013 15:17, Stephen Hemminger :
> It assumed another patch to allow different UIO driver devices.
> It hasn't been accepted, I presume because 6Wind doesn't like the patch
> because their drivers work differently.
This patch was reviewed but not approved because it was waiting a refactoring.
It assumed another patch to allow different UIO driver devices.
It hasn't been accepted, I presume because 6Wind doesn't like the patch
because their drivers work differently.
Subject: eal: support different modules
In order to support new devices, the module name should not be a boolean
flag to
On Fri, 09 Aug 2013 12:46:09 -0700
Patrick Mahan wrote:
> Stephen,
>
> When did you generate this diff? It failed to apply to 1.3.1r2 so I am hand
> patching instead. But you might want to update to the latest version.
>
> Thanks,
>
> Patrick
>
Diff was against current git HEAD
Stephen,
When did you generate this diff? It failed to apply to 1.3.1r2 so I am hand
patching instead. But you might want to update to the latest version.
Thanks,
Patrick
On 8/8/13 5:50 PM, Stephen Hemminger wrote:
> Still needs a little cleanup (patch is messy).
>
> Subject: pci: support mu
Still needs a little cleanup (patch is messy).
Subject: pci: support multiple PCI regions per device
Need to change PCI code to support multiple I/O regions on a single device.
Some devices like VMXNET3 have multiple PCI memory regions, and some
have none.
Signed-off-by: Stephen Hemminger
---
When?
I scanned the archives for this month and last month. I don't see any patches
regarding allowing other BARs to be mapped.
Thanks,
Patrick
Coming to you from deep inside Fortress Mahan
On Aug 8, 2013, at 4:53 PM, Stephen Hemminger
wrote:
> On Thu, 8 Aug 2013 16:45:42 -0700
> Patrick
On Thu, 8 Aug 2013 16:45:42 -0700
Patrick Mahan wrote:
> Before I do this, I wanted to check with the list.
>
> The UIO support code in DPDK only maps in bar 0 for PCI devices, and it does
> provide support for mapping any other bar that the device provides.
>
> Has anyone fixed this yet? Or
Before I do this, I wanted to check with the list.
The UIO support code in DPDK only maps in bar 0 for PCI devices, and it does
provide support for mapping any other bar that the device provides.
Has anyone fixed this yet? Or maybe has a patch?
DPDK version: 1.3.1r2
Thanks,
Patrick
8 matches
Mail list logo