Change MyISAM Locking Behaviour

[Irfan Ali]

We have overall read/write 80%/20% using MyISAM tables. Write queries are coming to slaves from Master Slaves are in use for SELECT queries from site.
I noticed locking issues on slaves. SELECT queries are in queue until INSERT/UPDATE/DELETE executes from replication thread. As per my knowledge FIFO (first in first out) algorithm works in MySQL. I want to change behavior of MyISAM.
I require SELECT's queries have to be exeuctes on top of UPDATE queries. Please let me know is it possible ?

To explain, let's take the test scenario.
1 I have 3 SELECT's queries first on table A.
2 After that 1 INSERT query on table A.
3 Then 1 UPDATE query on table A.
4 Then couple of SELECT's queries on table A.

I believe all sections executes in order from top to bottom i.e. from 1..4.
Is that possible to change it. I want it to be executes as 1,2,4,3.
SELECT queries should have higher priority from UPDATE queries. UPDATE shall be execute in last till no other select query on table A.
I believe it is possible from max_write_lock_count variable.