linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: staubach@redhat.com
Cc: akpm@linux-foundation.org, hugh@veritas.com,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] update ctime and mtime for mmaped write
Date: Wed, 21 Feb 2007 19:23:29 +0100	[thread overview]
Message-ID: <E1HJw7l-0003Tq-00@dorka.pomaz.szeredi.hu> (raw)
In-Reply-To: <45DC8A47.5050900@redhat.com> (message from Peter Staubach on Wed, 21 Feb 2007 13:07:03 -0500)

> > Inspired by Peter Staubach's patch and the resulting comments.
> >
> >   
> 
> An updated version of the original patch was submitted to LKML
> yesterday...  :-)

Strange coincidence :)

> >  		file = vma->vm_file;
> >  		start = vma->vm_end;
> > +		mapping_update_time(file);
> >  		if ((flags & MS_SYNC) && file &&
> >  				(vma->vm_flags & VM_SHARED)) {
> >  			get_file(file);
> >   
> 
> It seems to me that this might lead to file times being updated for
> non-MAP_SHARED mappings.

In theory no, because the COW-ed pages become anonymous and are not
part of the original mapping any more.

> > +int set_page_dirty_mapping(struct page *page);
> >   
> 
> This aspect of the design seems intrusive to me.  I didn't see a strong
> reason to introduce new versions of many of the routines just to handle
> these semantics.  What motivated this part of your design?  Why the new
> _mapping versions of routines?

Because there's no way to know inside the set_page_dirty() functions
if the dirtying comes from a memory mapping or from a modification
through a normal write().  And they have different semantics, for
write() the modification times are updated immediately.

Thanks,
Miklos

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-02-21 18:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21 17:51 Miklos Szeredi, Miklos Szeredi
2007-02-21 18:07 ` Peter Staubach
2007-02-21 18:23   ` Miklos Szeredi [this message]
2007-02-21 18:54     ` Peter Staubach
2007-02-21 19:07       ` Miklos Szeredi
2007-02-22 17:36         ` Peter Staubach
2007-02-22 18:16           ` Miklos Szeredi
2007-02-22 20:11             ` Peter Staubach
2007-02-22 20:43               ` Miklos Szeredi
2007-02-22 20:50                 ` Peter Staubach
2007-02-21 18:12 ` Trond Myklebust
2007-02-21 18:28   ` Miklos Szeredi
2007-02-21 18:36     ` Trond Myklebust
2007-02-21 18:50       ` Miklos Szeredi
2007-02-21 18:50       ` Peter Staubach
2007-02-22  4:26 ` Andrew Morton
2007-02-22  7:49   ` Miklos Szeredi
2007-02-22 17:39     ` Peter Staubach
2007-02-22 18:08       ` Miklos Szeredi
2007-02-22 20:14         ` Peter Staubach
2007-02-22 20:48           ` Miklos Szeredi
2007-02-22 20:55             ` Peter Staubach
2007-02-22 21:04             ` Trond Myklebust
2007-02-22 21:28               ` Miklos Szeredi
2007-02-22 21:52                 ` Peter Staubach
2007-02-22 22:08                   ` Miklos Szeredi

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=E1HJw7l-0003Tq-00@dorka.pomaz.szeredi.hu \
    --to=miklos@szeredi.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hugh@veritas.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=staubach@redhat.com \
    /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