Re: [PATCH] fadvise(2) system call



John Baldwin <jhb@xxxxxxxxxxx> wrote:

I have been working for the last week or so on a patch to add an
fadvise(2) system call. It is somewhat similar to madvise(2)
except that it operates on a file descriptor instead of a memory
region. It also only really makes sense for regular files and
does not apply to other file descriptor types.

Seems to me it could also make sense for disks and geoms. The
access patterns used by dump(8) and fsck(8) are likely different,
from each other and from those typically encountered in the course
of filesystem activity -- and I wouldn't be surprised if mounted
access patterns tended to differ among, say, ufs, zfs, and msdosfs.
Granted the pattern of disk activity created by a filesystem will
vary greatly, depending on the patterns of file access that the
filesystem is servicing.
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Red Hat 9 as PDC
    ... root# smbpasswd -a -m pentium ... etc/rc.d/rc.sysinit line 173 /dev/null Read Only Filesystem ... Initializing USB Controller dup2: Bad file descriptor ... Then again the same dev null stuff and then /boot clean ...
    (linux.redhat)
  • Re: [patch 3/5] VFS: pass open file to ->xattr()
    ... and it makes a lot of sense, if the filesystem has stateful opens. ... Similarly for any fs operation that gets a file descriptor, ... without that it's impossible to implement correct semantics in the ...
    (Linux-Kernel)
  • Re: [patch 3/5] VFS: pass open file to ->xattr()
    ... and it makes a lot of sense, if the filesystem has stateful opens. ... Similarly for any fs operation that gets a file descriptor, ... without that it's impossible to implement correct semantics in the ...
    (Linux-Kernel)
  • Re: [PATCH] VFS: new fgetattr() file operation
    ... We need this because fstat() semantics can in some cases be better ... implemented if the filesystem has the open file available. ... the server implemented as an unprivileged userspace process running on ... on a file descriptor obtained when the file was opened. ...
    (Linux-Kernel)
  • Re: kqueue, NOTE_EOF
    ... > AFAIK yes for sockets, not for file descriptor (i.e. descriptor open ... > event when on end of file on filesystem. ...
    (freebsd-hackers)