[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070712234159.GC4768@us.ibm.com>
Date: Thu, 12 Jul 2007 16:41:59 -0700
From: Mike Anderson <andmike@...ibm.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Alasdair G Kergon <agk@...hat.com>, dm-devel@...hat.com,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [2.6.23 PATCH 14/18] dm: netlink add to core
Eric W. Biederman <ebiederm@...ssion.com> wrote:
> As for worry about kmallocs do these events happen often?
The worst case would most likely be in a dm multipath configuration where
you could get a burst of N number events (N being equal to the number of
luns times the number of paths that are having an issue).
> I would
> not expect any of them in the normal course of operation for a system.
Yes, the ones that are part of this patch are unexpected events or
recovery of the unexpected event.
> Worst case you handle extra kmallocs with a library function.
> It's not like you are using GFP_ATOMIC.
I was using GFP_ATOMIC as I did not want __GFP_IO as in some testing there
was a case where heavy file system IO was going on and an injected error
event caused the swap device into a temporary queued condition while an
event was trying to be sent. I may need to go back and investigate this
case on recent kernels as it has been a while since I did the test case.
-andmike
--
Michael Anderson
andmike@...ibm.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists