From: Jason Wang <jasowang@redhat.com>
To: mst@redhat.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Jason Wang <jasowang@redhat.com>
Subject: [PATCH net-next 2/8] skb_array: introduce batch dequeuing
Date: Tue, 21 Mar 2017 12:04:41 +0800 [thread overview]
Message-ID: <1490069087-4783-3-git-send-email-jasowang@redhat.com> (raw)
In-Reply-To: <1490069087-4783-1-git-send-email-jasowang@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
---
include/linux/skb_array.h | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/include/linux/skb_array.h b/include/linux/skb_array.h
index f4dfade..90e44b9 100644
--- a/include/linux/skb_array.h
+++ b/include/linux/skb_array.h
@@ -97,21 +97,46 @@ static inline struct sk_buff *skb_array_consume(struct skb_array *a)
return ptr_ring_consume(&a->ring);
}
+static inline int skb_array_consume_batched(struct skb_array *a,
+ void **array, int n)
+{
+ return ptr_ring_consume_batched(&a->ring, array, n);
+}
+
static inline struct sk_buff *skb_array_consume_irq(struct skb_array *a)
{
return ptr_ring_consume_irq(&a->ring);
}
+static inline int skb_array_consume_batched_irq(struct skb_array *a,
+ void **array, int n)
+{
+ return ptr_ring_consume_batched_irq(&a->ring, array, n);
+}
+
static inline struct sk_buff *skb_array_consume_any(struct skb_array *a)
{
return ptr_ring_consume_any(&a->ring);
}
+static inline int skb_array_consume_batched_any(struct skb_array *a,
+ void **array, int n)
+{
+ return ptr_ring_consume_batched_any(&a->ring, array, n);
+}
+
+
static inline struct sk_buff *skb_array_consume_bh(struct skb_array *a)
{
return ptr_ring_consume_bh(&a->ring);
}
+static inline int skb_array_consume_batched_bh(struct skb_array *a,
+ void **array, int n)
+{
+ return ptr_ring_consume_batched_bh(&a->ring, array, n);
+}
+
static inline int __skb_array_len_with_tag(struct sk_buff *skb)
{
if (likely(skb)) {
--
2.7.4
next prev parent reply other threads:[~2017-03-21 4:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 4:04 [PATCH net-next 0/8] vhost-net rx batching Jason Wang
2017-03-21 4:04 ` [PATCH net-next 1/8] ptr_ring: introduce batch dequeuing Jason Wang
2017-03-21 10:25 ` Sergei Shtylyov
2017-03-22 3:16 ` Jason Wang
2017-03-22 13:43 ` Michael S. Tsirkin
2017-03-23 5:33 ` Jason Wang
2017-03-21 4:04 ` Jason Wang [this message]
2017-03-21 4:04 ` [PATCH net-next 3/8] tun: export skb_array Jason Wang
2017-03-21 4:04 ` [PATCH net-next 4/8] tap: " Jason Wang
2017-03-21 4:04 ` [PATCH net-next 5/8] tun: support receiving skb through msg_control Jason Wang
2017-03-21 4:04 ` [PATCH net-next 6/8] tap: support receiving skb from msg_control Jason Wang
2017-03-21 4:04 ` [PATCH net-next 7/8] vhost_net: try batch dequing from skb array Jason Wang
2017-03-22 14:16 ` Michael S. Tsirkin
2017-03-23 5:34 ` Jason Wang
2017-03-29 9:58 ` Jason Wang
2017-03-29 10:46 ` Pankaj Gupta
2017-03-29 10:53 ` Jason Wang
2017-03-29 21:47 ` Michael S. Tsirkin
2017-03-21 4:04 ` [PATCH net-next 8/8] vhost_net: use lockless peeking for skb array during busy polling Jason Wang
2017-03-29 12:07 ` Michael S. Tsirkin
2017-03-30 2:16 ` Jason Wang
2017-03-30 2:33 ` Michael S. Tsirkin
2017-03-30 3:53 ` Jason Wang
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=1490069087-4783-3-git-send-email-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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).