>> And if you check the amount of completely unneeded code Linux currently has >> just to implement e.g. SG_IO in /dev/hd*, it could even _save_ space in the >> kernel when converting to a clean SCSI based design. > >Please point me at that huge amount of code. Hint: there is none. I'm getting a grin: 15:46 takeshi:../drivers/ide > find . -type f -print0 | xargs -0 grep SG_IO (no results) Looks like it's already non-redundant :) Jan Engelhardt -- - 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: 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?)
- 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: 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: Rationale for RLIMIT_MEMLOCK?
- Prev by Date: Re: 2.6.16-rc1-mm3
- Next by Date: Re: Patch for CVE-2004-1334 ???
- 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) (was: Rationale for RLIMIT_MEMLOCK?)
- Index(es):
![]() |