From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] duppage
Date: Mon, 9 Jun 2014 09:21:35 -0400 [thread overview]
Message-ID: <8a89cb0cb2f6a8a0defb3b8af07a407c@brasstown.quanstro.net> (raw)
In-Reply-To: <CAOw7k5iytMqATUrz8ss4eiAeVpZCsMMdf1z-Hza4Dvsaocotmg@mail.gmail.com>
> On 8 June 2014 19:37, Charles Forsyth <charles.forsyth@gmail.com> wrote:
>
> > On 8 June 2014 19:15, erik quanstrom <quanstro@quanstro.net> wrote:
> >
> >> i think it is in the image cache, but .ref >1.
> >
> >
> > but in that case it will still not pio, but make a local writable copy.
>
>
> in fact ref > 1 is the copy-on-write case and in a sense the usual one,
> where the copy is needed.
i'll get back to this. after looking at the refcounting and thinking
about how imagealloc interacts with image allocation, the locking
scheme in imagereclaim does not make any sense.
- erik
next prev parent reply other threads:[~2014-06-09 13:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 14:53 erik quanstrom
2014-06-08 17:15 ` cinap_lenrek
2014-06-08 17:22 ` Charles Forsyth
2014-06-08 17:34 ` erik quanstrom
2014-06-08 17:50 ` Charles Forsyth
2014-06-08 17:53 ` erik quanstrom
2014-06-08 17:54 ` cinap_lenrek
2014-06-08 18:15 ` erik quanstrom
2014-06-08 18:37 ` Charles Forsyth
2014-06-09 8:23 ` Charles Forsyth
2014-06-09 13:21 ` erik quanstrom [this message]
2014-06-10 1:35 ` erik quanstrom
2014-06-10 3:53 ` cinap_lenrek
2014-06-10 12:58 ` erik quanstrom
2014-06-10 13:56 ` Steve Simon
2014-06-10 15:30 ` erik quanstrom
2014-06-10 14:06 ` cinap_lenrek
2014-06-11 18:04 ` erik quanstrom
2014-06-08 17:49 ` cinap_lenrek
-- strict thread matches above, loose matches on Subject: below --
2012-03-13 23:55 erik quanstrom
2012-02-25 3:29 cinap_lenrek
2012-02-25 20:09 ` Charles Forsyth
2012-02-26 4:13 ` erik quanstrom
2012-02-29 10:31 ` Richard Miller
2012-02-29 14:14 ` cinap_lenrek
2012-02-29 19:35 ` Richard Miller
2012-02-29 19:50 ` cinap_lenrek
2012-03-03 9:58 ` Richard Miller
2012-03-03 19:30 ` cinap_lenrek
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=8a89cb0cb2f6a8a0defb3b8af07a407c@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).