-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all I suspected that the anticipatory scheduler might not have been the best choice for video capture because of the interruption to writes by reads and the subsequent anticipatory delay associated with it. I have now confirmed that booting with the default anticipatory i/o elevator I get many dropped frames that I don't get if I boot with elevator=deadline. briefly: dual 7200 rpm ATA5 IDE drives in software RAID0 I guess there isn't really a lot to do about this, it's a compromise one way or the other. The anticipatory scheduler seems better all round but in this large streaming write situation it doesn't seem ideal. Any sysctl settings I could use to blunt the anticipation just before I do video capture? Con -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAD1qzZUg7+tp6mRURAuekAJ9pFVgSLkY7zr4TL7CEfdRfKdp1DQCfUC6T RnALyU70HgP9AQt8LS4+B6M= =H3WY -----END PGP SIGNATURE----- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: Deadline for video captureNick Piggin
- Prev by Date: Re: List 'linux-dvb' closed to public posts
- Next by Date: Re: KGDB 2.0.3 with fixes and development in ethernet interface
- Previous by thread: Re: [PATCH] rivafb & small 16 bit mode problem
- Next by thread: Re: Deadline for video capture
- Indexes:[Main][Thread]