From: Chuck Lever <cel@citi.umich.edu>
To: Olaf Kirch <okir@suse.de>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, nfs@lists.sourceforge.net
Subject: Re: NFS directio
Date: Fri, 31 Mar 2006 10:50:26 -0500 [thread overview]
Message-ID: <442D4FC2.7060109@citi.umich.edu> (raw)
In-Reply-To: <20060331145849.GF18629@suse.de>
Olaf Kirch wrote:
> On Fri, Mar 31, 2006 at 09:35:34AM -0500, Chuck Lever wrote:
>> the check isn't in 2.6.16. it was removed sometime after 2.6.5.
>
> It is still in the 2.6.16 tree I'm looking at; else I wouldn't ask :)
it's been in my trees since 2.6.13 or even earlier, my mistake.
that change is part of the aio+dio patches that were just included in
2.6.17-rc1. instead of creating a single patch for this change, you
should consider taking those patches, since they were tested as a unit.
if you can guarantee that atomic_t is 32-bits on every platform you
support, then it should be save to change that #define to 2^31.
otherwise, the work to eliminate the limit entirely has already been
done by the above-mentioned patches.
--
corporate: <cel at netapp dot com>
personal: <chucklever at bigfoot dot com>
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-03-31 15:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 15:15 NFS directio Olaf Kirch
2006-03-30 16:03 ` Trond Myklebust
2006-03-30 17:27 ` Chuck Lever
2006-03-31 7:49 ` Olaf Kirch
2006-03-31 14:35 ` Chuck Lever
2006-03-31 14:58 ` Olaf Kirch
2006-03-31 15:50 ` Chuck Lever [this message]
2006-04-09 12:38 ` Neil Brown
2006-04-09 22:09 ` Chuck Lever
2006-04-10 4:20 ` Neil Brown
2006-04-10 10:55 ` Olaf Kirch
2006-04-10 17:36 ` Chuck Lever
2006-04-11 0:12 ` Neil Brown
2006-04-11 0:47 ` Chuck Lever
2006-04-11 9:15 ` Olaf Kirch
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=442D4FC2.7060109@citi.umich.edu \
--to=cel@citi.umich.edu \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
--cc=trond.myklebust@fys.uio.no \
/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