Re: [Pvfs2-developers] help debugging request processor/distribution

2006-06-16 Thread Phil Carns
Pete Wyckoff wrote: [EMAIL PROTECTED] wrote on Wed, 14 Jun 2006 13:09 -0500: I've attached a patch of the sys-io state machine from trunk that doesn't post the flow until the initial response is received. Phil and Murali, can you let me know if this fixes your respective problems? Also,

Re: [Pvfs2-developers] patches: directory hints

2006-06-16 Thread Phil Carns
These patches are based on part of the functionality Murali originally contributed in this email thread: http://www.beowulf-underground.org/pipermail/pvfs2-developers/2005-November/001624.html Thanks for the patches! No, thank you - you did all of the hard work! Examples: [EMAIL PROTECTE

Re: [Pvfs2-developers] help debugging request processor/distribution

2006-06-16 Thread Murali Vilayannur
Hi Phil, > > I did find one odd result, although it is somewhat unrelated. In an > earlier email on this topic I mentioned that I was able to find a > temporary workaround for the bug by setting PVFS2_BUFMAP_DESC_COUNT to > 1, which limits pvfs2-client-core to only performing one I/O operation >

Re: [Pvfs2-developers] help debugging request processor/distribution

2006-06-16 Thread Rob Ross
if the processes were working on different files it is likely because the resulting i/o pattern is more sequential. Murali Vilayannur wrote: Hi Phil, I did find one odd result, although it is somewhat unrelated. In an earlier email on this topic I mentioned that I was able to find a temporar

Re: [Pvfs2-developers] msgpair error

2006-06-16 Thread Sam Lang
On Jun 15, 2006, at 2:20 PM, Pete Wyckoff wrote: [EMAIL PROTECTED] wrote on Thu, 15 Jun 2006 13:59 -0500: What's actually just as curious to me is that we don't ever call PINT_serv_free_msgpair_resources() in error cases if we *don't* succeed. Does this mean that every msgpairarray failure r

Re: [Pvfs2-developers] msgpair error

2006-06-16 Thread Pete Wyckoff
[EMAIL PROTECTED] wrote on Fri, 16 Jun 2006 17:05 -0500: > I haven't been able to reproduce this specific error or get dbench to > fail for me, but Murali just committed a bunch of fixes to bugs in > the keyval changes I made recently that I could imagine causing a lot > of weird behaviors.