On Mon, May 08, 2006 at 10:26:15PM +0200, Michael Kerrisk wrote:
> tags 365754 fixed-upstream
> thanks
> 
> Hello Justin,
> 
> [...]
> 
> > > Okay -- that look good.  But it's strange, I'm not seeing the
> > > same as you on SUSE 10.0, glibc 2.3.5.  Do you have another Linux
> > > to hand to test?
> > I just tested on another Debian machine with the same results for
> > fopen "rm".
> > 
> > But another machine did only an anonymous mmap:
> > 
> >   2.6.12-1-amd64-k8-smp
> >   glibc 2.3.6
> > 
> > I note the following differences:
> > Native POSIX Threads Library by Ulrich Drepper et al        and
> > libthread_db work sponsored by Alpha Processor Inc
> >     
> >     vs.
> > 
> > linuxthreads-0.10 by Xavier Leroy (on kobun64).
> > 
> > On a 32 bit radhat machine, the same thing; this time, linuxthreads
> > and libthread_db.  Linux 2.4.22-1.2199.nptl and glibc 2.3.3.
> > 
> > Alan didn't have strace installed on a different redhat machine, so I
> > copied mine, and again it didn't mmap the file.  Again, linuxthreads
> > and libthread_db.  glibc 2.3.3, and Linux 2.6.10-1.771_FC2.
> > 
> > I note that this functionality requires the compile-time conditional
> > _G_HAVE_MMAP.
> 
> Hmmm -- it is all a bit strange.  There are some other factors
> going on that aren't obvious.  Anyway, I've added the following
> text for man-pages-2.32:
> 
>        m (since glibc 2.3)
>               Attempt  to  access  the  file  using  mmap(2),
>               rather   than   I/O   system   calls  (read(2),
>               write(2)).  Currently, use of mmap(2)  is  only
>               attempted for a file opened for reading.
> 
> Thanks for you report and all the testing.
It occurs to me that this could be a part of the Debian patch; either
something not yet included upstream, or included in a release later
than glibc 2.3, but with the patch included by Debian anyway.

Google didn't reveal too much, and there's nothing in the .diff.gz
indicating that this is true .. I donno.

Justin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to