Re: [PATCH 8/8] cifs: use the server's MaxMpxCount to determine max requests in flight

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2011/5/6 Steve French <smfrench@xxxxxxxxx>:
> Two reserved slots:    1 for oplock break, 1 for echo.

What's if we need to send oplock break for two files in almost the same time?

> Note that if maxmpx is set to 2 on negotiate, we also have to disable
> oplock (echo + 1 pending open request would max out our maxmpx)

What's if maxmpx is set to 1? According to the link (that I posted
above) it is a possible situation.

Note that now we don't count block locking command, but the spec
doesn't tell anything about it - so, I think we should count them too.

May be we should drop any exceptions, count all types of requests and
move to smth like priority queue? In this case we can use three kind
of lists and put echo requests into the highest priority list - e.g.
"3", oplock break requests - "2", and all other requests into the
priority "1" list. Or we can use only one double-linked list and put
all echo and oplock break requests to the head, and all other requests
- to the tail.

Thoughts?

-- 
Best regards,
Pavel Shilovsky.
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux