From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Rusty Russell" <rusty@rustcorp.com.au>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
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 09:24:27 -0700 [thread overview]
Message-ID: <2c0942db0804180924n2ee701e5w7166a203569fc669@mail.gmail.com> (raw)
In-Reply-To: <200804190115.15983.rusty@rustcorp.com.au>
On Fri, Apr 18, 2008 at 8:15 AM, Rusty Russell <rusty@rustcorp.com.au> wrote:
> On Friday 18 April 2008 21:31:20 Andrew Morton wrote:
> > On Fri, 18 Apr 2008 14:43:24 +1000 Rusty Russell <rusty@rustcorp.com.au> wrote:
>
> > > + /* How many pages will this take? */
> > > + npages = 1 + (base + len - 1)/PAGE_SIZE - base/PAGE_SIZE;
> >
> > Brain hurts. I hope you got that right.
>
> I tested it when I wrote it, but just wrote a tester again:
>
> base len npages
> 0 1 1
> 0xfff 1 1
> 0x1000 1 1
> 0 4096 1
> 0x1 4096 2
> 0xfff 4096 2
> 0x1000 4096 1
> 0xfffff000 4096 1
> 0xfffff000 4097 4293918722
Picky, picky :-).
If base were always page aligned, we'd want
npages = (len + PAGE_SIZE - 1) / PAGE_SIZE;
which is simply rounding len up to the next largest page size. So when
base is not page aligned, increase len by the left-over space at the
beginning, and then do the same calculation as above. (ie, pretend
base is page aligned, and instead count the excess at the beginning as
part of len.)
npages = ( (base & PAGE_MASK) + len + PAGE_SIZE - 1) / PAGE_SIZE;
As long as len < PAGE_MASK - PAGE_SIZE, we're safe from overflows.
(The above gives a different answer when len=0, but you guard for that.)
next prev parent reply other threads:[~2008-04-18 16:24 UTC|newest]
Thread overview: 27+ 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:43 ` [PATCH 5/5] tun: vringfd xmit support Rusty Russell
2008-04-18 11:31 ` Andrew Morton
2008-04-18 15:15 ` Rusty Russell
2008-04-18 16:24 ` Ray Lee [this message]
2008-04-18 19:06 ` Andrew Morton
2008-04-19 14:41 ` Rusty Russell
2008-04-19 17:51 ` 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 18:01 ` pradeep singh rautela
2008-04-18 11:18 ` [PATCH 2/5] /dev/vring: simple userspace-kernel ringbuffer interface Andrew Morton
2008-04-18 14:32 ` Rusty Russell
2008-04-18 18:59 ` Andrew Morton
2008-04-18 19:38 ` Michael Kerrisk
2008-04-19 16:41 ` Rusty Russell
2008-04-20 0:16 ` David Miller
2008-04-19 15:02 ` Jonathan Corbet
2008-04-19 10:22 ` Evgeniy Polyakov
2008-04-19 16:05 ` Rusty Russell
2008-04-19 16:33 ` Evgeniy Polyakov
2008-04-19 16:45 ` 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=2c0942db0804180924n2ee701e5w7166a203569fc669@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®