On Wed, 2010-11-03 at 16:30 +0200, Aleksey Senin wrote:
The following patches add a new QP type named RAW_PACKET.
This type of QP is used in Ethernet environment and intended for
creation of a whole packet, including L2 headers, from userspace. In
order to prevent regular user from creating
Steve Wise wrote:
I'm working on similar code for Chelsio that will use these QPs.
Will the TX flow require going into kernel space or will be fully offloaded?
Or.
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More
On Fri, 2010-11-05 at 10:06 -0500, Steve Wise wrote:
On 11/03/2010 09:58 AM, Hefty, Sean wrote:
The following patches add a new QP type named RAW_PACKET.
This type of QP is used in Ethernet environment and intended for
creation of a whole packet, including L2 headers,
RAW_FRAME
On 11/03/2010 09:30 AM, Aleksey Senin wrote:
The following patches add a new QP type named RAW_PACKET.
This type of QP is used in Ethernet environment and intended for
creation of a whole packet, including L2 headers, from userspace. In
order to prevent regular user from creating malicious
On 11/03/2010 09:58 AM, Hefty, Sean wrote:
The following patches add a new QP type named RAW_PACKET.
This type of QP is used in Ethernet environment and intended for
creation of a whole packet, including L2 headers,
RAW_FRAME seems like a better name to me.
Not that it matters
Not that it matters much, but doesn't FRAME and PACKET mean the same
thing?
I associate frame with L2 and packet with L3. Since the user is expected to
provide the L2 header, frame seems clearer than packet. Then when someone
wants to introduce the RAW_PACKET where the user only provides
On 11/05/2010 10:15 AM, Hefty, Sean wrote:
Not that it matters much, but doesn't FRAME and PACKET mean the same
thing?
I associate frame with L2 and packet with L3. Since the user is expected to
provide the L2 header, frame seems clearer than packet. Then when someone
wants to
The linux PF_PACKET interface comes to mind. It allows
sending/receiving raw ethernet frames:
Packet sockets are used to receive or send raw packets at the
device
driver (OSI Layer 2) level. They allow the user to implement
protocol
modules in user space
On 11/05/2010 11:05 AM, Hefty, Sean wrote:
The linux PF_PACKET interface comes to mind. It allows
sending/receiving raw ethernet frames:
Packet sockets are used to receive or send raw packets at the
device
driver (OSI Layer 2) level. They allow the user to implement
Aleksey Senin wrote:
The following patches add a new QP type named RAW_PACKET.
Is there anything different in this patch set compared to V1 of
https://patchwork.kernel.org/patch/110153 or its just a repost?
Or.
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body
The following patches add a new QP type named RAW_PACKET.
This type of QP is used in Ethernet environment and intended for
creation of a whole packet, including L2 headers, from userspace. In
order to prevent regular user from creating malicious packets, at the
time of QP creation, kernel will
The following patches add a new QP type named RAW_PACKET.
This type of QP is used in Ethernet environment and intended for
creation of a whole packet, including L2 headers,
RAW_FRAME seems like a better name to me.
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
12 matches
Mail list logo
