On Thu, Nov 16, 2017 at 8:53 AM, Jesper Dangaard Brouer
wrote:
> On Wed, 15 Nov 2017 14:21:38 -0800
> chet l wrote:
>
>> One quick question:
>> Any thoughts on SVM support?
>
> What is SVM ?
>
Shared Virtual Memory(PCIe based). So going back to one of your
mapping examples. The protocol can be A
On Wed, Nov 15, 2017 at 5:44 PM, David Miller wrote:
> From: chet l
> Date: Wed, 15 Nov 2017 14:34:32 -0800
>
>> I have not reviewed the entire patchset but I think if we could add a
>> version_hdr and then unionize the fields, it might be easier to add
>> SVM support without having to spin v5. I
On Wed, 15 Nov 2017 14:21:38 -0800
chet l wrote:
> One quick question:
> Any thoughts on SVM support?
What is SVM ?
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
From: chet l
Date: Wed, 15 Nov 2017 14:34:32 -0800
> I have not reviewed the entire patchset but I think if we could add a
> version_hdr and then unionize the fields, it might be easier to add
> SVM support without having to spin v5. I could be wrong though.
Please, NO VERSION FIELDS!
Design th
On Tue, Oct 31, 2017 at 5:41 AM, Björn Töpel wrote:
> From: Björn Töpel
>
> +/*
> + * struct tpacket_memreg_req is used in conjunction with PACKET_MEMREG
> + * to register user memory which should be used to store the packet
> + * data.
> + *
> + * There are some constraints for the memory being
>
> Actually, we started out with that approach, where the packet_mmap
> call mapped Tx/Rx descriptor rings and the packet buffer region. We
> later moved to this (register umem) approach, because it's more
> flexible for user space, not having to use a AF_PACKET specific
> allocator (i.e. continue
2017-11-03 3:29 GMT+01:00 Willem de Bruijn :
+/*
+ * struct tpacket_memreg_req is used in conjunction with PACKET_MEMREG
+ * to register user memory which should be used to store the packet
+ * data.
+ *
+ * There are some constraints for the memory being registered:
>
>>> +/*
>>> + * struct tpacket_memreg_req is used in conjunction with PACKET_MEMREG
>>> + * to register user memory which should be used to store the packet
>>> + * data.
>>> + *
>>> + * There are some constraints for the memory being registered:
>>> + * - The memory area has to be memory page size
2017-11-02 17:40 GMT+01:00 Tushar Dave :
>
>
> On 11/02/2017 03:06 AM, Björn Töpel wrote:
>>
>> On 2017-11-02 02:45, Willem de Bruijn wrote:
>>>
>>> On Tue, Oct 31, 2017 at 9:41 PM, Björn Töpel
>>> wrote:
From: Björn Töpel
This patch adds the necessary AF_PACKET V4 structures
On 11/02/2017 03:06 AM, Björn Töpel wrote:
On 2017-11-02 02:45, Willem de Bruijn wrote:
On Tue, Oct 31, 2017 at 9:41 PM, Björn Töpel wrote:
From: Björn Töpel
This patch adds the necessary AF_PACKET V4 structures for usage from
userspace. AF_PACKET V4 is a new interface optimized for high
p
On 2017-11-02 02:45, Willem de Bruijn wrote:
> On Tue, Oct 31, 2017 at 9:41 PM, Björn Töpel wrote:
>> From: Björn Töpel
>>
>> This patch adds the necessary AF_PACKET V4 structures for usage from
>> userspace. AF_PACKET V4 is a new interface optimized for high
>> performance packet processing.
>>
On Tue, Oct 31, 2017 at 9:41 PM, Björn Töpel wrote:
> From: Björn Töpel
>
> This patch adds the necessary AF_PACKET V4 structures for usage from
> userspace. AF_PACKET V4 is a new interface optimized for high
> performance packet processing.
>
> Signed-off-by: Björn Töpel
> ---
> include/uapi/l
From: Björn Töpel
This patch adds the necessary AF_PACKET V4 structures for usage from
userspace. AF_PACKET V4 is a new interface optimized for high
performance packet processing.
Signed-off-by: Björn Töpel
---
include/uapi/linux/if_packet.h | 65 +-
1 f
13 matches
Mail list logo
