Re: [PATCH] Deadlock during heavy write activity to userspace NFS
From: Ulrich Weigand (weigand_at_i1.informatik.uni-erlangen.de)
Date: 07/28/04
- Previous message: David S. Miller: "Re: [PATCH][2.6] Allow x86_64 to reenable interrupts on contention"
- Next in thread: Avi Kivity: "Re: [PATCH] Deadlock during heavy write activity to userspace NFS"
- Reply: Avi Kivity: "Re: [PATCH] Deadlock during heavy write activity to userspace NFS"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: avi@exanet.com Date: Wed, 28 Jul 2004 04:32:03 +0200 (CEST)
Avi Kivity wrote:
>In our case, all block I/O is done using
>unbuffered I/O, and all memory is preallocated, so we don't need kswapd
>at all, just that small bit of memory that syscalls consume.
Does your userspace process need to send/receive network packets
in order to perform a write-out? If so, how can you make sure your
incoming packets aren't thrown away in out-of-memory situations?
(Outgoing packets can use PF_MEMALLOC memory I guess, but incoming
ones aren't associated to any process yet ...)
Bye,
Ulrich
-- Dr. Ulrich Weigand weigand@informatik.uni-erlangen.de - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Previous message: David S. Miller: "Re: [PATCH][2.6] Allow x86_64 to reenable interrupts on contention"
- Next in thread: Avi Kivity: "Re: [PATCH] Deadlock during heavy write activity to userspace NFS"
- Reply: Avi Kivity: "Re: [PATCH] Deadlock during heavy write activity to userspace NFS"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|