From: Jes Sorensen <jes@wildopensource.com>
To: libc-hacker@sources.redhat.com
Cc: Ray Bryant <raybry@sgi.com>
Subject: posix_fadvise() on ia64 and Alpha
Date: Fri, 18 Apr 2003 21:12:00 -0000 [thread overview]
Message-ID: <m3k7drwlvk.fsf@trained-monkey.org> (raw)
Whoops did it again - trying the right address this time.
Hi,
Ray Bry pointed out to me that there is a disreprency between the
glibc ia64 (and I noticed Alpha as well) definitions of
POSIX_FADV_DONTNEED and POSIX_FADV_NOREUSE compared to the kernel.
Anyone know if there is a deliberate reason for this or if it was a
mistake? I wont rule out that I blindly copied over the changes from
the Alpha back when I introduced the file, but it's been a while.
Anyway, for the case that it's unintentional, patch included (2.2),
should apply cleanly to 2.3 as well.
Cheers,
Jes
2003-04-18 <jes@wildopensource.com>
* libc/sysdeps/unix/sysv/linux/ia64/bits/fcntl.h: Sync with Linux
2.5.67.
* libc/sysdeps/unix/sysv/linux/alpha/bits/fcntl.h: Likewise.
--- sysdeps/unix/sysv/linux/ia64/bits/fcntl.h.~1.4.~ Fri Jul 6 00:56:17 2001
+++ sysdeps/unix/sysv/linux/ia64/bits/fcntl.h Fri Apr 18 16:55:49 2003
@@ -169,6 +169,6 @@
# define POSIX_FADV_RANDOM 1 /* Expect random page references. */
# define POSIX_FADV_SEQUENTIAL 2 /* Expect sequential page references. */
# define POSIX_FADV_WILLNEED 3 /* Will need these pages. */
-# define POSIX_FADV_DONTNEED 6 /* Don't need these pages. */
-# define POSIX_FADV_NOREUSE 7 /* Data will be accessed once. */
+# define POSIX_FADV_DONTNEED 4 /* Don't need these pages. */
+# define POSIX_FADV_NOREUSE 5 /* Data will be accessed once. */
#endif
--- sysdeps/unix/sysv/linux/alpha/bits/fcntl.h.~1.14.~ Fri Jul 6 00:56:13 2001
+++ sysdeps/unix/sysv/linux/alpha/bits/fcntl.h Fri Apr 18 16:57:48 2003
@@ -168,6 +168,6 @@
# define POSIX_FADV_RANDOM 1 /* Expect random page references. */
# define POSIX_FADV_SEQUENTIAL 2 /* Expect sequential page references. */
# define POSIX_FADV_WILLNEED 3 /* Will need these pages. */
-# define POSIX_FADV_DONTNEED 6 /* Don't need these pages. */
-# define POSIX_FADV_NOREUSE 7 /* Data will be accessed once. */
+# define POSIX_FADV_DONTNEED 4 /* Don't need these pages. */
+# define POSIX_FADV_NOREUSE 5 /* Data will be accessed once. */
#endif
next reply other threads:[~2003-04-18 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 21:12 Jes Sorensen [this message]
2003-04-19 18:33 ` Ulrich Drepper
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=m3k7drwlvk.fsf@trained-monkey.org \
--to=jes@wildopensource.com \
--cc=libc-hacker@sources.redhat.com \
--cc=raybry@sgi.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).