skb: report completion status for zero copy skbs
Even if skb is marked for zero copy, net core might still decide to copy it later which is somewhat slower than a copy in user context: besides copying the data we need to pin/unpin the pages. Add a parameter reporting such cases through zero copy callback: if this happens a lot, device can take this into account and switch to copying in user context. This patch updates all users but ignores the passed value for now: it will be used by follow-up patches. Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:

committed by
David S. Miller

parent
202975b4c5
commit
e19d6763cc
@@ -519,7 +519,7 @@ static void skb_release_data(struct sk_buff *skb)
|
||||
|
||||
uarg = skb_shinfo(skb)->destructor_arg;
|
||||
if (uarg->callback)
|
||||
uarg->callback(uarg);
|
||||
uarg->callback(uarg, true);
|
||||
}
|
||||
|
||||
if (skb_has_frag_list(skb))
|
||||
@@ -797,7 +797,7 @@ int skb_copy_ubufs(struct sk_buff *skb, gfp_t gfp_mask)
|
||||
for (i = 0; i < num_frags; i++)
|
||||
skb_frag_unref(skb, i);
|
||||
|
||||
uarg->callback(uarg);
|
||||
uarg->callback(uarg, false);
|
||||
|
||||
/* skb frags point to kernel buffers */
|
||||
for (i = num_frags - 1; i >= 0; i--) {
|
||||
|
Reference in New Issue
Block a user