linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Francis Moreau" <francis.moro@gmail.com>
To: "Hugh Dickins" <hugh@veritas.com>
Cc: a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org
Subject: Re: Re : vm: weird behaviour when munmapping
Date: Tue, 21 Nov 2006 09:41:22 +0100	[thread overview]
Message-ID: <38b2ab8a0611210041o2f5d251ale17082b951a90abb@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611201213460.11655@blonde.wat.veritas.com>

On 11/20/06, Hugh Dickins <hugh@veritas.com> wrote:
> On Mon, 20 Nov 2006, Francis Moreau wrote:
> >
> > I end up to see "open(B), close(B)" sequence when unmapping a part of
> > the dumb device that I found strange. I think that "open(A') close(B)"
> > can give more information to the driver and reflect that B is unmapped
> > and A' is still mapped and becomes the new mapped area.
> > But it's may be just me...
>
> I think I do now get your point.  But your way round doesn't really

my fault, I think I wasn't very clear when explaining myself

> reflect what's going on either: the range A' was already open and now
> you open it again.  Until there's some driver actually needing more
> sophisticated treatment, let's just leave it the simple way it is.

Yes, I agree that both ways are not satisfacting. Maybe having
vma->resize() method would have been better, I dunno.

Anyways thanks for your answers.
-- 
Francis

  reply	other threads:[~2006-11-21  8:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 21:01 Re : vm: weird behaviour when munmapping Francis Moreau
2006-11-18 13:55 ` Hugh Dickins
2006-11-20 11:30   ` Francis Moreau
2006-11-20 11:36     ` Hugh Dickins
2006-11-20 12:20     ` Hugh Dickins
2006-11-21  8:41       ` Francis Moreau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-17 14:12 moreau francis
2006-11-17 14:21 ` Peter Zijlstra
2006-11-17 13:43 moreau francis
2006-11-17 13:48 ` Peter Zijlstra
2006-11-17 12:50 moreau francis
2006-11-17 13:05 ` Peter Zijlstra

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=38b2ab8a0611210041o2f5d251ale17082b951a90abb@mail.gmail.com \
    --to=francis.moro@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@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).