From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@digeo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: wonderffffffffull ac filemap patch
Date: 27 Mar 2003 17:45:57 +0000 [thread overview]
Message-ID: <1048787156.3229.20.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0303271656270.2483-100000@localhost.localdomain>
On Thu, 2003-03-27 at 17:33, Hugh Dickins wrote:
> Here's a patch I've stolen from 2.4-ac, which is clearly correct so
> far as it goes. I keep wanting to get this integrated into 2.4 and
> 2.5, then bring shmem.c into line (in 2.5 use generic_write_checks).
>
> But each time I approach it, I get stuck on trying to understand the
> code it's a good patch to. I understand that there's a problem with
> loff_t twice as wide as rlim, and that we need to trim count down near
> the limit. But I don't understand why 0xFFFFFFFFULL and (u32) rather
> than RLIM_INFINITY and (unsigned long): are we really trying to
> cripple 64-bit arches here?
For 2.4 I just wanted to handle what we had and fix up the spec violations.
For 2.5.x rlimit64 is calling 8)
next prev parent reply other threads:[~2003-03-27 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 17:33 Hugh Dickins
2003-03-27 17:45 ` Alan Cox [this message]
2003-03-27 17:59 ` Hugh Dickins
2003-03-27 19:07 ` Alan Cox
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=1048787156.3229.20.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@digeo.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®