On Thu, Dec 2, 2010 at 2:19 AM, Or Gerlitz wrote:
> Alan, kernel patches posted to this mailing list are against the mainline
> (upstream) Linux kernel
Thanks for pointing me to the correct kernel.
I found Tom's patch from July, but was unsure if that was the patch in
question or not. It seems
On 12/1/2010 5:30 PM, Alan Cook wrote:
I am not able to find the patch that you submitted (bad search
terms?). I also am having a difficult time tracking down (with any
certainty) the sources that your patch would be made against.
Alan, kernel patches posted to this mailing list are against th
Tom Tucker writes:
> What I implemented was support for mmap'd memory. In practical terms for
> your application you would write a driver that supported the mmap file op.
> The driver's mmap routine would ioremap the pci memory of interest and
> stuff it in the provided vma. The user-mode app
On 11/30/10 9:24 AM, Alan Cook wrote:
Tom Tucker writes:
Yes. I removed the new verb and followed Jason's recommendation of adding
this support to the core reg_mr support. I used the type bits in the vma
struct to determine the type of memory being registered and just did the
"right thing."
I'
> Tom Tucker writes:
>
> Yes. I removed the new verb and followed Jason's recommendation of adding
> this support to the core reg_mr support. I used the type bits in the vma
> struct to determine the type of memory being registered and just did the
> "right thing."
>
> I'll repost in the the
On 11/29/10 11:10 AM, Steve Wise wrote:
On 11/24/2010 11:42 AM, Jason Gunthorpe wrote:
The last time this came up I said that the kernel side of ibv_reg_mr
should do the right thing for all types of memory that are mmap'd into
a process and I still think that is true. RDMA to device memory co
On 11/24/2010 11:42 AM, Jason Gunthorpe wrote:
The last time this came up I said that the kernel side of ibv_reg_mr
should do the right thing for all types of memory that are mmap'd into
a process and I still think that is true. RDMA to device memory could
be very useful and with things like G
Eli Cohen writes:
> You can't regiter IO memory using ibv_reg_mr() - you can only do that
> by registering that memory using physical memory registration which is
> available only for kernel consumers. You can't allow userspace to
> register physical pages as this is a security breach.
So, would
On Wed, Nov 24, 2010 at 03:55:07PM +0200, Eli Cohen wrote:
> On Mon, Nov 22, 2010 at 06:28:47PM +, Brian wrote:
> > ibv_reg_mr works fine as long as the shared region is in RAM. However, if I
> > change the memory region to the physical memory on a PCI device the call to
> > ibv_reg_mr fails. W
On Mon, Nov 22, 2010 at 06:28:47PM +, Brian wrote:
> ibv_reg_mr works fine as long as the shared region is in RAM. However, if I
> change the memory region to the physical memory on a PCI device the call to
> ibv_reg_mr fails. What should I be doing to register a physical memory region?
>
> In
ibv_reg_mr works fine as long as the shared region is in RAM. However, if I
change the memory region to the physical memory on a PCI device the call to
ibv_reg_mr fails. What should I be doing to register a physical memory region?
In searching through this forum I've seen some patches relating to
11 matches
Mail list logo
