One thing I would like to mention is that when I do a priocntl -l, it shows only the SYSTEM, INTERACTIVE, and the TIMESHARE classes. REALTIME does not appear in that list. But when I issue the command *priocntl -e -c RT -p 59 "path to the executable"*, then priocntl does not complain. Infact, I see that process running with priority 159, and nice value -20. Looks fine to me, but it doesn't seem that the application does any better in terms of emptying the socket buffer! Is it running in the real-time mode?
Thank you, Vishal On Thu, Apr 22, 2010 at 12:42 PM, Joerg Schilling < joerg.schill...@fokus.fraunhofer.de> wrote: > Jason King <ja...@ansipunx.net> wrote: > > > IIRC, Real time processes have higher priority than even the kernel, > > so one should be _very_ careful about putting applications in the the > > RT class, as a poorly written app can cause bad things to happen. > > You _can_ put a user process at a higher priority than the kernel tasks > (like > the pager). You should only do this with gode that does not consume all the > CPU. > Check the man pages for the real time priority levels compared to other > tasks. > > Start e.g. with man priocntl > > Jörg > > -- > > EMail:jo...@schily.isdn.cs.tu-berlin.de<email%3ajo...@schily.isdn.cs.tu-berlin.de>(home) > Jörg Schilling D-13353 Berlin > j...@cs.tu-berlin.de (uni) > joerg.schill...@fokus.fraunhofer.de (work) Blog: > http://schily.blogspot.com/ > URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily >
_______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
