CVS log for pvfs2/src/io/dev/pint-dev-shared.h
	Help

Request diff between arbitrary revisions / Display revisions graphically

merge with Orange-Branch

Committed Windows client code to Orange-Branch.

Porting flow etc.

Reverse merged and ported to HEAD.

Machines without ioctl will complain on the uses of _IOR and so forth,
as well as ioctl, poll calls.  The code to implement getting requests
through a character device runs through about 12 files in the source
tree.  Rather than hacking out all the linux-kmod-related bits, selectively
disable just the main commands but leave it all harmlessly compiled in.
A new configure variable tells if a linux kernel module was requested.

Merge HEAD changes to TAS-branch.

walt3 reverse merge from head includes merges of pw's sm changes (no state declarations), cleanup of state machine code, and other general merging/fixes.

Update migration branch to current CVS version

Sync hint-branch to current CVS version

merge 2.6 branch changes to head

Synchronization with HEAD

quiet some general warnings

merge of murali's kernel buffer size tuning options to HEAD.

murali's patch to allow tuning kernel buffer settings from client-core.

backmerging of HEAD to branch...

Merge HEAD into Walt's branch.
Rework new state machines to the new cleanups introduced by Walt.

Merge posix-extensions-branch to HEAD
This branch implemented patches to the 2.6.16 kernel for the proposed POSIX I/O extensions and those patches are under
the patches subdirectory.
It also implements the PVFS2 specific hooks for these system calls.

Tools that may be of immediate use to the pvfs2 general audience is the pvfs2-lsplus utility in src/apps/admin
that should be noticeably faster than the pvfs2-ls utility if there are a lot of objects in a single directory.
Other features are left out by configure and are not even built if the kernels do not support those features
and callbacks.

Reverse merges from HEAD..

reverse merge from trunk.  working for now.

Gossip'ized kmod as well so that we dont have 2 separate calls to printing diagnostics.
gossip for the kmod is fairly primitive and is handled simply by means of a macro in gossip.h.
Replaced and removed pvfs2_print and pvfs2_error with gossip_debug.
Edited quickstart to include comments on the new kmod debug parameters as well.

Includes reverse merges from trunk
in addition, it includes fixes for readdir and readdirplus to have a variable length
number of directory entries passed in from client-core using a trailer page (currently).
However, there is nothing that prevents us from sharing those pages with the kernel using vmap
and friends which is the next logical step.
So client-core now does a readdir/readdirplus and writev's the trailer page (which is essentially
an encoded version of the readdir/readdirplus response) to the kmod.
The kernel module decodes that and copies it to the user-space app (which issued the getdents/getdents_plus
system call)
Added/edited the getdents.c test program in the test/posix sub directory to issue
getdents/getdents64/getdents_plus/getdents64_plus system calls
Also fixed a critical bug that was somehow never triggered in readdir if the buffer size
provided by glibc/user was not sufficient enough and we advance the f_pos token beyond where we stopped.

the <sys/ioctl.h> header is not available when building the kernel, so we have
to use <linux/ioctl.h> in that case.

fix warnings and errors on darwin

commit of murali's 64bit fixes.

[pcarns]: add a protocol version to the pvfs2 device communication.  ensures
clients and the kernel module come from the same source tree, but also has the
pleasing side effect of 8-byte aligning access to the header of the request.

- applied cleanups and annotations to pass the 'sparse' analysis tests
  more information about sparse is at:
  http://groups.google.com/groups?hl=en&lr=&selm=2VezS-rN-3%40gated-at.bofh.it

- we still get 'sparse' warnings due to a function that we use for both reading
  data into kernel buffers (via readpage for mmap) and user buffers (for normal
  file_read calls).  without redundant code, there's no trivial way to get
  around the warning, so it remains for now.
- due to preprocessor elimination of the annotations used, this appears to also
  work on 2.4.x kernels and setups that don't understand the annotations
- misc cleanups

- more mmap-readahead cruft removal while improving and simplifying usage
- misc cleanups

- applied Nathan's expandtab patch (expandtab-2.patch.gz)

  first referenced at:
  http://www.beowulf-underground.org/pipermail/pvfs2-developers/2004-July/000745.html

this fixes 3 separate things reported by robl and phil.  this changelog lists
phil's description and a description of the fix:

---
1) This one isn't too bad, but if I run this:
      ./pvfs2-client -p pvfs2-client-core
   instead of this:
      ./pvfs2-client -p ./pvfs2-client-core
  ... the output looks the same either way (ie, it appears successful).
In the former case, both the client and client-core actually exited,
because i specified the path to the core incorrectly.  It would be nice
if it printed something in this case to avoid confusion.
---

Ok, done...this is tricky because if the client-core is in the same dir as
the client program, a 'stat' will pass, but the execvp may fail if that dir
isn't in the system PATH.  Now, we print an error if the path is not absolute
and the client core exits.

---
2) I don't know if this happens everywhere or not, but I am running on a
box here where bad things happen if I get the hostname wrong on the
mount command, for example doing something like this:
        mount -t pvfs2 tcp://a43:0/pvfs2-fs /mnt/pvfs2
(note that the port is wrong).  Sorry I didn't catch this when you asked
me to try this stuff out the other day :(  At any rate, the mount command
segfaults, and I get this in dmesg:

Attempting PVFS2 Mount via host tcp://a43:0/pvfs2-fs
Got an unknown pvfs2 error code: -1073741967
pvfs2_fs_mount: got return value of -1073741967
Unable to handle kernel paging request at virtual address 733d4853
 printing eip:
 c016b062
 *pde = 00000000
---

This is due to an error code translation problem.  Previously, the kernel
code didn't translate all pvfs_errno codes to actual errno codes, so I've
re-worked the error code translation functions so that they can be shared
by the kernel and the user space code.

---
3) This one is kinda nasty, and I'm not sure what's going wrong yet.
The scenario is that I have successfully mounted, but then on the next
operation (a getattr), the communication fails causing the msgpair.sm to
call exit(1).  The pvfs2-client and client-core then exit.  I start them
back up, and nothing ever works again.  I get "Input/output error" any
time I try to access pvfs2 from then on, and I get "can't write
superblock" when I try to unmount.  I have to reboot the box to get back
to sanity.
---

This turned out to be a beast of a problem now that we have dynamic mounts on
the client side.  The issue is that on cancelled i/o, or on pvfs2-client-core
restart, there's *no* way the kernel can associate upcalls with the client-core
anymore because the dynamic mount information is lost forever as far as the
client-core is concerned.

The solution I chose for this is to have the pvfs2-client-core issue an ioctl
that causes the kernel to do mount upcalls for every pvfs2 file system it knows
about to avoid having to have the user manually issue another mount command
(or something goofy like that).  Other solutions that I considered and didn't
like are 1) having the pvfs2-client-core store mount info in a file somewhere
and have it remount those on startup, or 2) having the pvfs2-client and
pvfs2-client-core have some ipc going on so that the pvfs2-client can store
the mount info and somehow give it back to the pvfs2-client-core on restart.
both of those are shoddy at best, and do not seem robust at all (i.e.
stale file info will error out on stale remount attempts, ipc requires that
the pvfs2-client never dies along with the pvfs2-client-core, etc).

With the current solution, we have all the information that the kernel knows
about (and so it's more reliable than a file or something), and it's the most
natural way to hand the information up from the kernel (since we have to do
this via upcalls anyway).  Thus, the kernel code now keeps a list of pvfs2
superblocks and we store the info given to the sb at mount time so that it
can dynamically be remounted at any time.  The pvfs2-client-core now issues
an ioctl (in a thread so that it can still service the request) on startup
to 'remount' any file systems the kernel knows about.  while I'm calling this
a remount, it's basically just a mechanism for the kernel to tell the client
core enough information ot rebuild the dynamic mount tables in the system
interface.

because of this, the pvfs2-client-core program *requires* pthreads.  This is
completely independent of whether or not the PVFS2 sysint needs pthreads
at all.

- change a constant to allow for safer comparison
- change db error handling callback to not dump backtraces when reporting
  errors (if enabled)
- add some gossip

fixes 'du' size reporting through the vfs interface

- implemented readahead mmap/execution caching in pvfs2-client-core
  to optimize the vfs' small block behaviour that normally hurts
  performance on pvfs2 significantly.  this is the initial implementation
  and probably needs work.

temporary breakage shuffling kernel related constants around; some debug
statements were added I guess

user level hooks for getting kernel/user shared buffer

now we\'re stylin

filled in write function; untested

added ioctls to read some startup parameters from device; added a header file
with some information that needs to be shared between kernel and user level