On Fri, Nov 02, 2012 at 09:59:07PM +0100, Michael Kerrisk wrote: > John, > > A question at on one point: > > On Wed, Oct 3, 2012 at 12:38 AM, John Stultz <john.stultz@xxxxxxxxxx> wrote: > > On 10/02/2012 12:39 AM, NeilBrown wrote: > [...] > >> The SIGBUS interface could have some merit if it really reduces > >> overhead. I > >> worry about app bugs that could result from the non-deterministic > >> behaviour. A range could get unmapped while it is in use and testing > >> for > >> the case of "get a SIGBUS half way though accessing something" would not > >> be straight forward (SIGBUS on first step of access should be easy). > >> I guess that is up to the app writer, but I have never liked anything > >> about > >> the signal interface and encouraging further use doesn't feel wise. > > > > Initially I didn't like the idea, but have warmed considerably to it. Mainly > > due to the concern that the constant unmark/access/mark pattern would be too > > much overhead, and having a lazy method will be much nicer for performance. > > But yes, at the cost of additional complexity of handling the signal, > > marking the faulted address range as non-volatile, restoring the data and > > continuing. > > At a finer level of detail, how do you see this as happening in the > application. I mean: in the general case, repopulating the purged > volatile page would have to be done outside the signal handler (I > think, because async-signal-safety considerations would preclude too > much compdex stuff going on inside the handler). That implies > longjumping out of the handler, repopulating the pages with data, and > then restarting whatever work was being done when the SIGBUS was > generated. There are different strategies that can be used to repopulate the pages, within or outside the signal handler, and I'd say it's not that important of a detail. That being said, if the kernel could be helpful and avoid people shooting themselves in the foot, that would be great, too. I don't know how possible this would be but being able to get the notification on a signalfd in a dedicated thread would certainly improve things (I guess other usecases of SIGSEGV/SIGBUG handlers could appreciate something like this). The kernel would pause the faulting thread while sending the notification on the signalfd, and the notified thread would be allowed to resume the faulting thread when it's done doing its job. Mike -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>