Displaying 3 results from an estimated 3 matches for "virtnet_release_receive_queue_stat".
Did you mean:
virtnet_release_receive_queue_stats
2014 Jan 07
0
[PATCH net-next v2 4/4] virtio-net: initial debugfs support, export mergeable rx buffer size
..._ERR_OR_NULL(debugfs_rename(virtnet_debugfs_root,
+ vi->dbg_dev_root,
+ virtnet_debugfs_root, dev->name))) {
+ pr_warn("%s: failed debugfs rename, removing old debugfs dir\n",
+ dev->name);
+ virtnet_debugfs_cleanup(vi);
+ }
+ return NOTIFY_DONE;
+}
+
+static void virtnet_release_receive_queue_stats(struct virtnet_info *vi)
+{
+ int i;
+
+ for (i = 0; i < vi->max_queue_pairs; i++) {
+ struct receive_queue_stats *rq_stats = vi->rq_stats[i];
+ if (rq_stats)
+ kref_put(&rq_stats->refcount, receive_queue_stats_free);
+ }
+ kfree(vi->rq_stats);
+}
+
static int virtnet_probe...
2014 Jan 07
10
[PATCH net-next v2 1/4] net: allow > 0 order atomic page alloc in skb_page_frag_refill
skb_page_frag_refill currently permits only order-0 page allocs
unless GFP_WAIT is used. Change skb_page_frag_refill to attempt
higher-order page allocations whether or not GFP_WAIT is used. If
memory cannot be allocated, the allocator will fall back to
successively smaller page allocs (down to order-0 page allocs).
This change brings skb_page_frag_refill in line with the existing
page allocation
2014 Jan 07
10
[PATCH net-next v2 1/4] net: allow > 0 order atomic page alloc in skb_page_frag_refill
skb_page_frag_refill currently permits only order-0 page allocs
unless GFP_WAIT is used. Change skb_page_frag_refill to attempt
higher-order page allocations whether or not GFP_WAIT is used. If
memory cannot be allocated, the allocator will fall back to
successively smaller page allocs (down to order-0 page allocs).
This change brings skb_page_frag_refill in line with the existing
page allocation