linux-mips
[Top] [All Lists]

Re: fadvise on MIPS

To: linux-mips@linux-mips.org
Subject: Re: fadvise on MIPS
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Date: Wed, 07 Mar 2007 00:35:53 +0900 (JST)
In-reply-to: <20070303.012914.15243240.anemo@mba.ocn.ne.jp>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20070217.004329.108739438.anemo@mba.ocn.ne.jp> <20070217.004812.03978264.anemo@mba.ocn.ne.jp> <20070303.012914.15243240.anemo@mba.ocn.ne.jp>
Sender: linux-mips-bounce@linux-mips.org
On Sat, 03 Mar 2007 01:29:14 +0900 (JST), Atsushi Nemoto <anemo@mba.ocn.ne.jp> 
wrote:
> > For N32 and O32, kernel should be fixed anyway, but which syscall
> > should be supported?  And whether kernel or libc should take care of
> > 'long long' issue?
> 
> Then how about this absolutely untested patch?

I had forgotten changing __NR_Linux_syscalls, etc.  And I found
readahead() has same problem, and sys32_readahead() and
sys32_sync_file_range() does not match with glibc.  I'll send a new
patch, fixing them all in kernel side.

---
Atsushi Nemoto

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