On Wed, Apr 27, 2011 at 7:51 AM, Hugh Dickins <hughd@xxxxxxxxxx> wrote: > On Mon, Apr 25, 2011 at 5:42 PM, Geunsik Lim <leemgs1@xxxxxxxxx> wrote: >> I will modify contents that you commented. > > Thank you for making the effort, but we would much prefer to eliminate > ZAP_BLOCK_SIZE than have a configurable ZAP_BLOCK_SIZE. ÂSo I don't > think you need update the contents here. > > Peter's preemptible mmu_gather work is expected to be included in the > next mmotm. ÂPlease test on that, and if it does not meet your needs, > do let us know. Thank you comments. As I answered to Peter, When we are running Linux kernel at a various system (e.g: Server/Desktop/Embedded), If preemptible mmu_gather work is sufficient to get real-fast or real-time(= preemptive property?) selectively, I am ok. > > Thanks, > Hugh > -- Regards, Geunsik Lim ( Samsung Electronics ) Blog : http://blog.naver.com/invain/ e-Mail: geunsik.lim@xxxxxxxxxxx     Â leemgs@xxxxxxxxx , leemgs1@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
