From: "David S. Miller" <davem@redhat.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: hugh@veritas.com, willy@debian.org, linux-kernel@vger.kernel.org,
parisc-linux@lists.parisc-linux.org, drepper@redhat.com
Subject: Re: [parisc-linux] Re: Problems with kernel mmap (failing tst-mmap-eofsync in glibc on parisc)
Date: Sat, 23 Aug 2003 15:53:12 -0700 [thread overview]
Message-ID: <20030823155312.63f996f6.davem@redhat.com> (raw)
In-Reply-To: <1061677283.1992.471.camel@mulgrave>
On 23 Aug 2003 17:21:21 -0500
James Bottomley <James.Bottomley@SteelEye.com> wrote:
> On Sat, 2003-08-23 at 16:43, David S. Miller wrote:
> > On 22 Aug 2003 20:09:30 -0500
> > James Bottomley <James.Bottomley@SteelEye.com> wrote:
> >
> > > To avoid having to flush the non-shared mappings (basically on parisc if
> > > you write to a file backing a MAP_PRIVATE mapping then we don't
> > > guarantee you see the update).
BTW, what gains to you really get from this optimization?
How often do writes happen to files while private mappings
to it exist? :-) This is one of the reasons I think this
discussion is a bit silly.
What specific cases does your optimization help, and how common is it?
Show us some numbers.
next prev parent reply other threads:[~2003-08-23 23:00 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 14:40 [parisc-linux] Problems with kernel mmap (failing tst-mmap-eofsync in glibc on parisc) James Bottomley
2003-08-22 14:40 ` James Bottomley
2003-08-22 16:14 ` [parisc-linux] " David S. Miller
2003-08-22 16:14 ` David S. Miller
2003-08-22 16:14 ` David S. Miller
2003-08-22 16:34 ` [parisc-linux] " Matthew Wilcox
2003-08-22 16:34 ` Matthew Wilcox
2003-08-22 16:39 ` David S. Miller
2003-08-22 17:41 ` Matthew Wilcox
2003-08-22 17:41 ` Matthew Wilcox
2003-08-22 17:36 ` David S. Miller
2003-08-22 17:36 ` David S. Miller
2003-08-22 18:01 ` David S. Miller
2003-08-22 18:01 ` David S. Miller
2003-08-22 18:34 ` Hugh Dickins
2003-08-22 18:34 ` Hugh Dickins
2003-08-22 18:31 ` David S. Miller
2003-08-22 18:56 ` James Bottomley
2003-08-22 19:19 ` David S. Miller
2003-08-22 19:19 ` David S. Miller
2003-08-22 22:27 ` James Bottomley
2003-08-22 22:41 ` David S. Miller
2003-08-22 22:41 ` David S. Miller
2003-08-23 1:09 ` James Bottomley
2003-08-23 7:22 ` Hugh Dickins
2003-08-23 7:22 ` Hugh Dickins
2003-08-23 15:59 ` James Bottomley
2003-08-23 15:59 ` James Bottomley
2003-08-23 21:44 ` David S. Miller
2003-08-23 21:44 ` David S. Miller
2003-08-23 21:43 ` David S. Miller
2003-08-23 22:21 ` James Bottomley
2003-08-23 22:21 ` James Bottomley
2003-08-23 22:51 ` David S. Miller
2003-08-23 23:01 ` James Bottomley
2003-08-23 23:01 ` James Bottomley
2003-08-23 22:51 ` David S. Miller
2003-08-23 22:53 ` David S. Miller [this message]
2003-08-23 23:11 ` James Bottomley
2003-08-23 23:11 ` James Bottomley
2003-08-24 0:22 ` David S. Miller
2003-08-24 5:17 ` James Bottomley
2003-08-24 5:23 ` David S. Miller
2003-08-24 16:54 ` James Bottomley
2003-08-24 16:54 ` James Bottomley
2003-08-24 0:22 ` David S. Miller
2003-08-23 22:53 ` David S. Miller
2003-08-23 21:43 ` David S. Miller
2003-08-23 1:09 ` James Bottomley
2003-08-22 22:27 ` James Bottomley
2003-08-22 18:56 ` James Bottomley
2003-08-22 18:31 ` David S. Miller
2003-08-22 18:41 ` James Bottomley
2003-08-22 19:02 ` Hugh Dickins
2003-08-22 19:02 ` Hugh Dickins
2003-08-22 19:09 ` Randolph Chung
2003-08-22 19:09 ` Randolph Chung
2003-08-22 18:41 ` James Bottomley
2003-08-22 16:39 ` David S. Miller
2003-08-22 16:42 ` Russell King
2003-08-22 16:39 ` David S. Miller
2003-08-22 16:39 ` David S. Miller
2003-08-22 16:42 ` Russell King
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=20030823155312.63f996f6.davem@redhat.com \
--to=davem@redhat.com \
--cc=James.Bottomley@SteelEye.com \
--cc=drepper@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.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.