From: David Miller <davem@davemloft.net>
To: doronrk@fb.com
Cc: davejwatson@fb.com, vakul.garg@nxp.com, borisp@mellanox.com,
aviadye@mellanox.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next,v4] net/tls: Calculate nsg for zerocopy path without skb_cow_data.
Date: Mon, 20 Aug 2018 17:30:01 -0700 (PDT) [thread overview]
Message-ID: <20180820.173001.605297842206917126.davem@davemloft.net> (raw)
In-Reply-To: <20180821002723.GA79644@doronrk-mbp>
From: Doron Roberts-Kedes <doronrk@fb.com>
Date: Mon, 20 Aug 2018 17:27:23 -0700
> Given that frag_lists are not unlikely in this case, I believe the only
> remaining feedback on the original patch was the recursive
> implementation. If you'd like, I can re-submit with an iterative
> implementation, but I noticed that goes against the existing recursive
> pattern in functions like skb_release_data -> kfree_skb_list -> kfree_skb
> -> __kfree_skb -> skb_release_all -> skb_release_data, as well as
> skb_to_sgvec. Let me know whether an iterative implementation is
> preferred here, or whether I can simply rebase and resubmit a patch
> similar to the original (modulo some variable renaming improvements).
Ok, I guess staying with the recursive implementation is fine.
It's a real shame that frag lists are so common in this code path,
especially nested ones :-/
In the long term, perhaps we can do something about that.
In the short term, I guess this means your original change is OK.
Please resubmit when the net-next tree opens back up, thanks.
prev parent reply other threads:[~2018-08-21 3:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 18:09 [PATCH net-next,v4] net/tls: Calculate nsg for zerocopy path without skb_cow_data Doron Roberts-Kedes
2018-08-08 19:14 ` David Miller
2018-08-09 22:43 ` Doron Roberts-Kedes
2018-08-11 18:54 ` David Miller
2018-08-21 0:27 ` Doron Roberts-Kedes
2018-08-21 0:30 ` David Miller [this message]
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=20180820.173001.605297842206917126.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=davejwatson@fb.com \
--cc=doronrk@fb.com \
--cc=netdev@vger.kernel.org \
--cc=vakul.garg@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).