[lkml]   [2009]   [Sep]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [ofa-general] Re: [GIT PULL] please pull ummunotify

> > > Hmm, or are you saying you can only get 1 event per registered range and
> > > allocate the thing on registration? That'd need some registration limit
> > > to avoid DoS scenarios.
> >
> > Yes, that's what I do. You're right, I should add a limit... although
> > their are lots of ways for userspace to consume arbitrary amounts of
> > kernel resources already.
> I'd be good to work at reducing that number, not adding to it ;-)

Yes, definitely. I'll add a quick ummunotify module parameter that
limits the number of registrations per process.

> But yeah, I currently don't see a very nice match to perf counters.

OK. It would be nice to tie into something more general, but I think I
agree -- perf counters are missing the filtering and the "no lost
events" that ummunotify does have. And I'm not sure it's worth messing
up the perf counters design just to jam one more not totally related
thing in.

- R.

 \ /
  Last update: 2009-09-17 17:47    [W:0.106 / U:11.448 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site