From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Fan Du <fan.du@windriver.com>,
steffen.klassert@secunet.com, davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH RFC 1/5] {pktgen, xfrm} Remove original pktgen ipsec fixed configuration
Date: Thu, 05 Dec 2013 18:00:05 +0400 [thread overview]
Message-ID: <52A086E5.1050701@cogentembedded.com> (raw)
In-Reply-To: <1386230239-31860-2-git-send-email-fan.du@windriver.com>
Hello.
On 05-12-2013 11:57, Fan Du wrote:
> Cleanup original fixed IPsec output mode and encapuslation type,
> As following patchset enable user to configure IPsec attribute.
> Signed-off-by: Fan Du <fan.du@windriver.com>
> ---
> net/core/pktgen.c | 11 +++--------
> 1 file changed, 3 insertions(+), 8 deletions(-)
> diff --git a/net/core/pktgen.c b/net/core/pktgen.c
> index a797fff..ab67986 100644
> --- a/net/core/pktgen.c
> +++ b/net/core/pktgen.c
> @@ -387,8 +387,7 @@ struct pktgen_dev {
> int node; /* Memory node */
>
> #ifdef CONFIG_XFRM
> - __u8 ipsmode; /* IPSEC mode (config) */
> - __u8 ipsproto; /* IPSEC type (config) */
> +
Why add this empty line which you'll remove in patch #3? And I'd also have
removed empty #ifdef too...
> #endif
> char result[512];
> };
> @@ -2482,10 +2481,7 @@ static int pktgen_output_ipsec(struct sk_buff *skb, struct pktgen_dev *pkt_dev)
>
> if (!x)
> return 0;
> - /* XXX: we dont support tunnel mode for now until
> - * we resolve the dst issue */
> - if (x->props.mode != XFRM_MODE_TRANSPORT)
> - return 0;
> +
Why? There's enough empty lines already.
>
> spin_lock(&x->lock);
>
> @@ -3540,8 +3536,7 @@ static int pktgen_add_device(struct pktgen_thread *t, const char *ifname)
> goto out2;
> }
> #ifdef CONFIG_XFRM
> - pkt_dev->ipsmode = XFRM_MODE_TRANSPORT;
> - pkt_dev->ipsproto = IPPROTO_ESP;
> +
Same question about empty line removed in patch #3.
> #endif
WBR, Sergei
next prev parent reply other threads:[~2013-12-05 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 7:57 [PATCH RFC 0/5] pktgen IPsec support Fan Du
2013-12-05 7:57 ` [PATCH RFC 1/5] {pktgen, xfrm} Remove original pktgen ipsec fixed configuration Fan Du
2013-12-05 14:00 ` Sergei Shtylyov [this message]
2013-12-05 7:57 ` [PATCH RFC 2/5] {pktgen, xfrm} Using "pgset spi xxx" to spedifiy SA for a given flow Fan Du
2013-12-05 7:57 ` [PATCH RFC 3/5] {pktgen,xfrm} Construct skb dst for tunnel mode transformation Fan Du
2013-12-05 7:57 ` [PATCH RFC 4/5] {pktgen, xfrm} Introduce xfrm_state_lookup_byspi for pktgen Fan Du
2013-12-05 7:57 ` [PATCH RFC 5/5] {pktgen, xfrm} Correct xfrm state lock usage when transforming Fan Du
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=52A086E5.1050701@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=fan.du@windriver.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.