From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 net-next 5/7] tun: support receiving skb through msg_control
Date: Thu, 30 Mar 2017 18:06:28 +0300 [thread overview]
Message-ID: <20170330180414-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1490858550-7763-6-git-send-email-jasowang@redhat.com>
On Thu, Mar 30, 2017 at 03:22:28PM +0800, Jason Wang wrote:
> This patch makes tun_recvmsg() can receive from skb from its caller
> through msg_control. Vhost_net will be the first user.
>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
Do we need to bother with tun? I didn't realize one
can even use that with vhost. What would be the point of
all the virtio header stuff dealing with checksums etc?
Even if you see a use-case is it worth optimizing?
> ---
> drivers/net/tun.c | 18 ++++++++++--------
> 1 file changed, 10 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/net/tun.c b/drivers/net/tun.c
> index 70dd9ec..a82bced 100644
> --- a/drivers/net/tun.c
> +++ b/drivers/net/tun.c
> @@ -1498,9 +1498,8 @@ static struct sk_buff *tun_ring_recv(struct tun_file *tfile, int noblock,
>
> static ssize_t tun_do_read(struct tun_struct *tun, struct tun_file *tfile,
> struct iov_iter *to,
> - int noblock)
> + int noblock, struct sk_buff *skb)
> {
> - struct sk_buff *skb;
> ssize_t ret;
> int err;
>
> @@ -1509,10 +1508,12 @@ static ssize_t tun_do_read(struct tun_struct *tun, struct tun_file *tfile,
> if (!iov_iter_count(to))
> return 0;
>
> - /* Read frames from ring */
> - skb = tun_ring_recv(tfile, noblock, &err);
> - if (!skb)
> - return err;
> + if (!skb) {
> + /* Read frames from ring */
> + skb = tun_ring_recv(tfile, noblock, &err);
> + if (!skb)
> + return err;
> + }
>
> ret = tun_put_user(tun, tfile, skb, to);
> if (unlikely(ret < 0))
> @@ -1532,7 +1533,7 @@ static ssize_t tun_chr_read_iter(struct kiocb *iocb, struct iov_iter *to)
>
> if (!tun)
> return -EBADFD;
> - ret = tun_do_read(tun, tfile, to, file->f_flags & O_NONBLOCK);
> + ret = tun_do_read(tun, tfile, to, file->f_flags & O_NONBLOCK, NULL);
> ret = min_t(ssize_t, ret, len);
> if (ret > 0)
> iocb->ki_pos = ret;
> @@ -1634,7 +1635,8 @@ static int tun_recvmsg(struct socket *sock, struct msghdr *m, size_t total_len,
> SOL_PACKET, TUN_TX_TIMESTAMP);
> goto out;
> }
> - ret = tun_do_read(tun, tfile, &m->msg_iter, flags & MSG_DONTWAIT);
> + ret = tun_do_read(tun, tfile, &m->msg_iter, flags & MSG_DONTWAIT,
> + m->msg_control);
> if (ret > (ssize_t)total_len) {
> m->msg_flags |= MSG_TRUNC;
> ret = flags & MSG_TRUNC ? ret : total_len;
> --
> 2.7.4
next prev parent reply other threads:[~2017-03-30 15:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 7:22 [PATCH V2 net-next 0/7] vhost-net rx batching Jason Wang
2017-03-30 7:22 ` [PATCH V2 net-next 1/7] ptr_ring: introduce batch dequeuing Jason Wang
2017-03-30 13:53 ` Michael S. Tsirkin
2017-03-31 3:52 ` Jason Wang
2017-03-31 14:31 ` Michael S. Tsirkin
2017-04-01 5:14 ` Jason Wang
2017-03-30 7:22 ` [PATCH V2 net-next 2/7] skb_array: " Jason Wang
2017-03-30 7:22 ` [PATCH V2 net-next 3/7] tun: export skb_array Jason Wang
2017-03-30 7:22 ` [PATCH V2 net-next 4/7] tap: " Jason Wang
2017-03-30 7:22 ` [PATCH V2 net-next 5/7] tun: support receiving skb through msg_control Jason Wang
2017-03-30 15:06 ` Michael S. Tsirkin [this message]
2017-03-31 4:10 ` Jason Wang
2017-03-30 7:22 ` [PATCH V2 net-next 6/7] tap: support receiving skb from msg_control Jason Wang
2017-03-30 15:03 ` Michael S. Tsirkin
2017-03-31 4:07 ` Jason Wang
2017-03-30 7:22 ` [PATCH V2 net-next 7/7] vhost_net: try batch dequing from skb array Jason Wang
2017-03-30 14:21 ` Michael S. Tsirkin
2017-03-31 4:02 ` Jason Wang
2017-03-31 6:47 ` 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=20170330180414-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).