From: Andrew Morton <akpm@linux-foundation.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Max Krasnyansky <maxk@qualcomm.com>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 5/5] tun: vringfd xmit support.
Date: Fri, 18 Apr 2008 04:31:20 -0700 [thread overview]
Message-ID: <20080418043120.ff78eab5.akpm@linux-foundation.org> (raw)
In-Reply-To: <200804181443.24812.rusty@rustcorp.com.au>
On Fri, 18 Apr 2008 14:43:24 +1000 Rusty Russell <rusty@rustcorp.com.au> wrote:
> This patch modifies tun to allow a vringfd to specify the send
> buffer. The user does a write to push out packets from the buffer.
>
> Again we use the 'struct virtio_net_hdr' to allow userspace to send
> GSO packets. In this case, it can hint how much to copy, and the
> other pages will be made into skb fragments.
>
>
> ...
>
> +/* We don't consolidate consecutive iovecs, so huge iovecs can break here.
> + * Users will learn not to do that. */
> +static int get_user_skb_frags(const struct iovec *iv, size_t len,
> + struct skb_frag_struct *f)
> +{
> + unsigned int i, j, num_pg = 0;
> + int err;
> + struct page *pages[MAX_SKB_FRAGS];
> +
> + down_read(¤t->mm->mmap_sem);
> + while (len) {
> + int n, npages;
> + unsigned long base, len;
> + base = (unsigned long)iv->iov_base;
> + len = (unsigned long)iv->iov_len;
> +
> + if (len == 0) {
> + iv++;
> + continue;
> + }
> +
> + /* How many pages will this take? */
> + npages = 1 + (base + len - 1)/PAGE_SIZE - base/PAGE_SIZE;
Brain hurts. I hope you got that right.
> + if (unlikely(num_pg + npages > MAX_SKB_FRAGS)) {
> + err = -ENOSPC;
> + goto fail;
> + }
> + n = get_user_pages(current, current->mm, base, npages,
> + 0, 0, pages, NULL);
What is the maximum numbet of pages which an unpriviliged user can
concurrently pin with this code?
> + if (unlikely(n < 0)) {
> + err = n;
> + goto fail;
> + }
> +
> + /* Transfer pages to the frag array */
> + for (j = 0; j < n; j++) {
> + f[num_pg].page = pages[j];
> + if (j == 0) {
> + f[num_pg].page_offset = offset_in_page(base);
> + f[num_pg].size = min(len, PAGE_SIZE -
> + f[num_pg].page_offset);
> + } else {
> + f[num_pg].page_offset = 0;
> + f[num_pg].size = min(len, PAGE_SIZE);
> + }
> + len -= f[num_pg].size;
> + base += f[num_pg].size;
> + num_pg++;
> + }
This loop is a fancy way of doing
num_pg = n;
> + if (unlikely(n != npages)) {
> + err = -EFAULT;
> + goto fail;
> + }
why not do this immediately after running get_user_pages()?
> + }
> + up_read(¤t->mm->mmap_sem);
> + return num_pg;
> +
> +fail:
> + for (i = 0; i < num_pg; i++)
> + put_page(f[i].page);
release_pages() could be a tad more efficient, but it's only error-path.
> + up_read(¤t->mm->mmap_sem);
> + return err;
> +}
> +
>
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: netdev@vger.kernel.org, Max Krasnyansky <maxk@qualcomm.com>,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] tun: vringfd xmit support.
Date: Fri, 18 Apr 2008 04:31:20 -0700 [thread overview]
Message-ID: <20080418043120.ff78eab5.akpm@linux-foundation.org> (raw)
In-Reply-To: <200804181443.24812.rusty@rustcorp.com.au>
On Fri, 18 Apr 2008 14:43:24 +1000 Rusty Russell <rusty@rustcorp.com.au> wrote:
> This patch modifies tun to allow a vringfd to specify the send
> buffer. The user does a write to push out packets from the buffer.
>
> Again we use the 'struct virtio_net_hdr' to allow userspace to send
> GSO packets. In this case, it can hint how much to copy, and the
> other pages will be made into skb fragments.
>
>
> ...
>
> +/* We don't consolidate consecutive iovecs, so huge iovecs can break here.
> + * Users will learn not to do that. */
> +static int get_user_skb_frags(const struct iovec *iv, size_t len,
> + struct skb_frag_struct *f)
> +{
> + unsigned int i, j, num_pg = 0;
> + int err;
> + struct page *pages[MAX_SKB_FRAGS];
> +
> + down_read(¤t->mm->mmap_sem);
> + while (len) {
> + int n, npages;
> + unsigned long base, len;
> + base = (unsigned long)iv->iov_base;
> + len = (unsigned long)iv->iov_len;
> +
> + if (len == 0) {
> + iv++;
> + continue;
> + }
> +
> + /* How many pages will this take? */
> + npages = 1 + (base + len - 1)/PAGE_SIZE - base/PAGE_SIZE;
Brain hurts. I hope you got that right.
> + if (unlikely(num_pg + npages > MAX_SKB_FRAGS)) {
> + err = -ENOSPC;
> + goto fail;
> + }
> + n = get_user_pages(current, current->mm, base, npages,
> + 0, 0, pages, NULL);
What is the maximum numbet of pages which an unpriviliged user can
concurrently pin with this code?
> + if (unlikely(n < 0)) {
> + err = n;
> + goto fail;
> + }
> +
> + /* Transfer pages to the frag array */
> + for (j = 0; j < n; j++) {
> + f[num_pg].page = pages[j];
> + if (j == 0) {
> + f[num_pg].page_offset = offset_in_page(base);
> + f[num_pg].size = min(len, PAGE_SIZE -
> + f[num_pg].page_offset);
> + } else {
> + f[num_pg].page_offset = 0;
> + f[num_pg].size = min(len, PAGE_SIZE);
> + }
> + len -= f[num_pg].size;
> + base += f[num_pg].size;
> + num_pg++;
> + }
This loop is a fancy way of doing
num_pg = n;
> + if (unlikely(n != npages)) {
> + err = -EFAULT;
> + goto fail;
> + }
why not do this immediately after running get_user_pages()?
> + }
> + up_read(¤t->mm->mmap_sem);
> + return num_pg;
> +
> +fail:
> + for (i = 0; i < num_pg; i++)
> + put_page(f[i].page);
release_pages() could be a tad more efficient, but it's only error-path.
> + up_read(¤t->mm->mmap_sem);
> + return err;
> +}
> +
>
next prev parent reply other threads:[~2008-04-18 11:31 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 4:33 [PATCH 0/5] High-speed tun receive and xmit Rusty Russell
2008-04-18 4:35 ` [PATCH 1/5] virtio: put last_used and last_avail index into ring itself Rusty Russell
2008-04-18 4:39 ` [PATCH 2/5] /dev/vring: simple userspace-kernel ringbuffer interface Rusty Russell
2008-04-18 4:41 ` [PATCH 3/5] /dev/vring limit and base ioctls Rusty Russell
2008-04-18 4:42 ` [PATCH 4/5] tun: vringfd receive support Rusty Russell
2008-04-18 4:42 ` Rusty Russell
2008-04-18 4:43 ` [PATCH 5/5] tun: vringfd xmit support Rusty Russell
2008-04-18 11:31 ` Andrew Morton [this message]
2008-04-18 11:31 ` Andrew Morton
2008-04-18 15:15 ` Rusty Russell
2008-04-18 15:15 ` Rusty Russell
2008-04-18 16:24 ` Ray Lee
2008-04-18 16:24 ` Ray Lee
2008-04-18 19:06 ` Andrew Morton
2008-04-18 19:06 ` Andrew Morton
2008-04-19 14:41 ` Rusty Russell
2008-04-19 17:51 ` Andrew Morton
2008-04-19 17:51 ` Andrew Morton
2008-04-19 14:41 ` Rusty Russell
2008-04-19 1:54 ` Andrew Morton
2008-04-19 1:54 ` Andrew Morton
2008-04-18 11:46 ` pradeep singh rautela
2008-04-18 14:25 ` Ray Lee
2008-04-18 14:25 ` Ray Lee
2008-04-18 18:01 ` pradeep singh rautela
2008-04-18 18:01 ` pradeep singh rautela
2008-04-18 4:43 ` Rusty Russell
2008-04-18 4:43 ` Rusty Russell
2008-04-18 4:41 ` [PATCH 3/5] /dev/vring limit and base ioctls Rusty Russell
2008-04-18 11:18 ` [PATCH 2/5] /dev/vring: simple userspace-kernel ringbuffer interface Andrew Morton
2008-04-18 11:18 ` Andrew Morton
2008-04-18 14:32 ` Rusty Russell
2008-04-18 14:32 ` Rusty Russell
2008-04-18 18:59 ` Andrew Morton
2008-04-18 18:59 ` Andrew Morton
2008-04-18 19:38 ` Michael Kerrisk
2008-04-18 19:38 ` Michael Kerrisk
2008-04-19 16:41 ` Rusty Russell
2008-04-20 0:16 ` David Miller
2008-04-20 0:16 ` David Miller
2008-04-19 16:41 ` Rusty Russell
2008-04-19 15:02 ` Jonathan Corbet
2008-04-19 15:02 ` Jonathan Corbet
2008-04-19 10:22 ` Evgeniy Polyakov
2008-04-19 10:22 ` Evgeniy Polyakov
2008-04-19 16:05 ` Rusty Russell
2008-04-19 16:05 ` Rusty Russell
2008-04-19 16:33 ` Evgeniy Polyakov
2008-04-19 16:33 ` Evgeniy Polyakov
2008-04-19 16:45 ` Rusty Russell
2008-04-19 16:45 ` Rusty Russell
2008-04-18 4:39 ` Rusty Russell
2008-04-18 4:35 ` [PATCH 1/5] virtio: put last_used and last_avail index into ring itself Rusty Russell
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=20080418043120.ff78eab5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.