On Tue, Aug 26, 2014 at 11:24 AM, Matt W. Benjamin <matt@xxxxxxxxxxxx> wrote: > IIUC, the problem is the forechannel slot count, since the call you want to make synchronously is on the forechannel? Yep. layoutcommit will be sent on the fore channel, which is why it can deadlock with the initial layoutget (or whatever operation that triggered the layout recall). > Matt > > ----- "Boaz Harrosh" <boaz@xxxxxxxxxxxxx> wrote: > >> On 08/26/2014 05:55 PM, Trond Myklebust wrote: >> > On Tue, Aug 26, 2014 at 10:37 AM, Boaz Harrosh <boaz@xxxxxxxxxxxxx> >> wrote: >> > >> > The above can deadlock if there are no session slots available to >> send >> > the layoutcommit, in which case the recall won't complete, and the >> > layoutget won't get a reply (which would free up the slot). >> > >> >> What? the back-channel and the fore-channel do not use the same >> slots. these are two different slots, No? >> >> Matt, Adam you need to chip in here. >> >> If it is as you say, then yes it must be as Christoph wrote it. >> >> And the Ganesha server must be fixed because it has a slot system per >> channel. >> >> Thanks >> Boaz > > -- > Matt Benjamin > The Linux Box > 206 South Fifth Ave. Suite 150 > Ann Arbor, MI 48104 > > http://linuxbox.com > > tel. 734-761-4689 > fax. 734-769-8938 > cel. 734-216-5309 -- Trond Myklebust Linux NFS client maintainer, PrimaryData trond.myklebust@xxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
