* deadlock encountered for my network file system
@ 2004-04-27 8:24 Rongfeng Tang
0 siblings, 0 replies; only message in thread
From: Rongfeng Tang @ 2004-04-27 8:24 UTC (permalink / raw)
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
Hi all,
I'm encountering a deadlock problem within kernel(2.4.19smp):
A lot of data writen into a network file system and the physical memory is almost exhausted, so that the kswapd calls the kswapd_balance -> try_to_free_pages->...->shrink_cache try to free a dirty page(just name it PageA) of the file system. the file system's writepage locks the page and sends the data to a dedicated process (named ProcB)of this file system in the same node which just send the data to remote server. ProcB communicates with server by TCP/IP. when the TCP/IP layer try to alloc a free page for transmission, it also arouse the kernel to free some dirty pages, what's a pity, the PageA has been selected. Since it's locked now , the shrink_cache just calls on wait_on_page, thus a big deadlock is generated.
Is it a bug? if not, please give me some advice on how to just out of this cycle.
Thanks
Rongfeng
[-- Attachment #2: fox.gif --]
[-- Type: image/gif, Size: 9519 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-04-27 8:30 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-04-27 8:24 deadlock encountered for my network file system Rongfeng Tang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®