> > On 6/17/15 1:56 AM, kan.li...@intel.com wrote: > > diff --git a/tools/perf/util/event.c b/tools/perf/util/event.c index > > 793b150..ac6cf2a 100644 > > --- a/tools/perf/util/event.c > > +++ b/tools/perf/util/event.c > > @@ -213,6 +213,8 @@ static int perf_event__synthesize_fork(struct > perf_tool *tool, > > return 0; > > } > > > > +#define MMAP_TIMEOUT (50 * 1000000ULL) > > + > > How did you determine 50msec is a good time? This seems really low to me > considering the range of platforms supported by perf and various run time > conditions. The default needs to work right on all platforms. >
I only test 50ms on my platforms. For all platforms, any recommendation? > Why not have the default be infinity and users who need the feature use > the option provided in patch 2? If we set the default to infinity, the user will get nothing when perf top runs in our case. There will be no warning. How do they know that they should change the time out limit? So I still think we need a finite default value. The problem is what's the number. Thanks, Kan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
