Jens Axboe <axboe@suse.de> wrote: > It just looks like Joerg needs to do his homework, before spreading > false information on lkml. Then again, all his "arguments" are the same > as last time (and the time before, and before, and so on). Before spreading your false claims, please do your homework. We previously had mostly fruitful discussion before you did appear. Please either try to contribute useful ideas or stay out. Jörg -- EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@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: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jens Axboe <axboe@suse.de>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- References:
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Arjan van de Ven <arjan@infradead.org>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Lee Revell <rlrevell@joe-job.com>
- CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jan Engelhardt <jengelh@linux01.gwdg.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jens Axboe <axboe@suse.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jan Engelhardt <jengelh@linux01.gwdg.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jens Axboe <axboe@suse.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- Prev by Date: Re: [patch, lock validator] fix uidhash_lock <-> RCU deadlock
- Next by Date: [patch, validator] fix proc_subdir_lock related deadlock
- Previous by thread: Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- Next by thread: Re: CD writing in future Linux (stirring up a hornets' nest)
- Index(es):
![]() |