0696, released
Oct 1. But kernel (2.6.22.5) still hangs up. Kernel with this fix patch boots
and works fine.
> Thanks for letting us know. So, another reason to drop this patch :)
>
> thanks,
>
> greg k-h
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Thanks,
Vitaliy Gusev
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
Thanks,
Vitaliy Gusev
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
On the Friday 21 September 2007 16:37 Trond Myklebust, wrote:
> On Fri, 2007-09-21 at 13:13 +0400, Vitaliy Gusev wrote:
> > Hello.
> >
> > Tested kernels: 2.6.18, 2.6.22, 2.6.23-rc2
> >
> > Steps to reproduce: Suppose that we have mounted some directory from nfs
&
:
nfs_find_actor()
{
...
if (nfs_compare_fh(NFS_FH(inode), fh))
return 0;
...
}
Therefore for each of hard links new struct inode is allocated. It leads to
cache aliasing.
Please explain why nfs_find_actor() function compares file handles?
--
Thanks,
Vitaliy Gusev
#include
#include
:
nfs_find_actor()
{
...
if (nfs_compare_fh(NFS_FH(inode), fh))
return 0;
...
}
Therefore for each of hard links new struct inode is allocated. It leads to
cache aliasing.
Please explain why nfs_find_actor() function compares file handles?
--
Thanks,
Vitaliy Gusev
#include
#include
:
nfs_find_actor()
{
...
if (nfs_compare_fh(NFS_FH(inode), fh))
return 0;
...
}
Therefore for each of hard links new struct inode is allocated. It leads to
cache aliasing.
Please explain why nfs_find_actor() function compares file handles?
--
Thanks,
Vitaliy Gusev
#include stdio.h
:
nfs_find_actor()
{
...
if (nfs_compare_fh(NFS_FH(inode), fh))
return 0;
...
}
Therefore for each of hard links new struct inode is allocated. It leads to
cache aliasing.
Please explain why nfs_find_actor() function compares file handles?
--
Thanks,
Vitaliy Gusev
#include stdio.h
On the Friday 21 September 2007 16:37 Trond Myklebust, wrote:
On Fri, 2007-09-21 at 13:13 +0400, Vitaliy Gusev wrote:
Hello.
Tested kernels: 2.6.18, 2.6.22, 2.6.23-rc2
Steps to reproduce: Suppose that we have mounted some directory from nfs
v3 server with default options. Also we
8 matches
Mail list logo
