linux-mips
[Top] [All Lists]

Re: User applications

To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>, linux-mips@oss.sgi.com
Subject: Re: User applications
From: Michael Shmulevich <michaels@jungo.com>
Date: Tue, 09 Jan 2001 13:49:29 +0200
References: <Pine.GSO.3.96.1010108185713.23234R-100000@delta.ds2.pg.gda.pl>
Sender: owner-linux-mips@oss.sgi.com
As a side question, I would like to to know why exactly the CPU cache operations
are
promoted to the syscall status? What is the situation that a user in its program
would like
to call cacheflush() ? Unless, of course, he is doing DoS.

I can understand why we need this in kernel, for context switch, for example, 
but
as a syscall?...

Michael.

"Maciej W. Rozycki" wrote:

> On Mon, 8 Jan 2001, Ralf Baechle wrote:
>
> > > $ mipsel-linux-objdump -T /usr/mipsel-linux/lib/libc-2.2.so | grep 
> > > cachectl
> > > 00000000600ca0a0  w   DF *ABS*  0000000000000000  GLIBC_2.0   cachectl
> > > $ ls /usr/mipsel-linux/include/sys/cachectl.h
> > > /usr/mipsel-linux/include/sys/cachectl.h
> >
> > cachectl(2) is a syscall that is manipulates the cachability of a memory
> > area.  And not yet implemented ...
>
>  s/cachectl$/cacheflush/, of course (but the header is still valid).
>
> --
> +  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
> +--------------------------------------------------------------+
> +        e-mail: macro@ds2.pg.gda.pl, PGP key available        +


<Prev in Thread] Current Thread [Next in Thread>