From: Roman Mashak <mrv@mojatatu•com>
To: Yotam Gigi <yotamg@mellanox•com>
Cc: jhs@mojatatu•com, davem@davemloft•net, netdev@vger•kernel.org,
eladr@mellanox•com, jiri@mellanox•com
Subject: Re: [PATCH 2/3] net: Introduce ife encapsulation module
Date: Fri, 03 Feb 2017 08:31:14 -0500 [thread overview]
Message-ID: <85k297o0yl.fsf@mojatatu.com> (raw)
In-Reply-To: <1485955803-65065-3-git-send-email-yotamg@mellanox.com> (Yotam Gigi's message of "Wed, 1 Feb 2017 15:30:02 +0200")
Yotam Gigi <yotamg@mellanox•com> writes:
> This module is responsible for the ife encapsulation protocol
> encode/decode logics. That module can:
> - ife_encode: encode skb and reserve space for the ife meta header
> - ife_decode: decode skb and extract the meta header size
> - ife_tlv_meta_encode - encodes one tlv entry into the reserved ife
> header space.
> - ife_tlv_meta_decode - decodes one tlv entry from the packet
> - ife_tlv_meta_next - advance to the next tlv
>
> Reviewed-by: Jiri Pirko <jiri@mellanox•com>
> Signed-off-by: Yotam Gigi <yotamg@mellanox•com>
Signed-off-by: Roman Mashak <mrv@mojatatu•com>
--
Roman Mashak
next prev parent reply other threads:[~2017-02-03 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 13:30 [PATCH v2 net-next 0/3] Extract IFE logic to module Yotam Gigi
2017-02-01 13:30 ` [PATCH 1/3] net/sched: act_ife: Unexport ife_tlv_meta_encode Yotam Gigi
2017-02-03 13:05 ` Jamal Hadi Salim
2017-02-03 13:30 ` Roman Mashak
2017-02-01 13:30 ` [PATCH 2/3] net: Introduce ife encapsulation module Yotam Gigi
2017-02-03 13:06 ` Jamal Hadi Salim
2017-02-03 13:31 ` Roman Mashak [this message]
2017-02-01 13:30 ` [PATCH 3/3] net/sched: act_ife: Change to use ife module Yotam Gigi
2017-02-03 13:08 ` Jamal Hadi Salim
2017-02-03 13:31 ` Roman Mashak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85k297o0yl.fsf@mojatatu.com \
--to=mrv@mojatatu$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=eladr@mellanox$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@mellanox$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=yotamg@mellanox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox