Dear Wolfgang,
The work flow is that:
Every timeout is reached, it will call NfsSend() and whatever the state is
finally it will call rpc_req() which will increase the rpc_id value every
time. The rpc_id value is increased but the reply.id is not increased by
timeout. This makes the
Dear Jin Qing-B24347,
In message
f37f9b48e0e59d42a5f9491a3cad99ad7e8...@zch01exm28.fsl.freescale.net you wrote:
The work flow is that:
Every timeout is reached, it will call NfsSend() and whatever the
state is finally it will call rpc_req() which will increase the rpc_id
value every
Dear Wolfgang
The work flow is that:
Every timeout is reached, it will call NfsSend() and whatever the
state is finally it will call rpc_req() which will increase the
rpc_id value every time. The rpc_id value is increased but the
reply.id is not increased by timeout. This makes the
From: Jin Qing b24...@freescale.com
The NFS_TIMEOUT is 2s before. It is too short for some nfs server to respond.
Signed-off-by: Jin Qing b24...@freescale.com
---
We are not sure what is the expected timeout period. Using 20s to make sure
the mount works.
net/nfs.c |2 +-
1 files
Dear Li Yang,
In message 1281947653-5530-1-git-send-email-le...@freescale.com you wrote:
From: Jin Qing b24...@freescale.com
The NFS_TIMEOUT is 2s before. It is too short for some nfs server to respond.
Signed-off-by: Jin Qing b24...@freescale.com
---
We are not sure what is the
On Mon, Aug 16, 2010 at 6:09 PM, Wolfgang Denk w...@denx.de wrote:
Dear Li Yang,
In message 1281947653-5530-1-git-send-email-le...@freescale.com you wrote:
From: Jin Qing b24...@freescale.com
The NFS_TIMEOUT is 2s before. It is too short for some nfs server to
respond.
Signed-off-by:
Dear Li Yang,
In message aanlkti=o6z1ebm1af94zp5-s6_3vf6ttp2vedhdzw...@mail.gmail.com you
wrote:
#define NFS_RETRY_COUNT 30
-#define NFS_TIMEOUT 2000UL
+#define NFS_TIMEOUT 2UL
You mean 30 retries (NFS_RETRY_COUNT) every two seconds were not
sufficient in your case?
That's
7 matches
Mail list logo
