| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 04 Feb 2008 19:25:42 +0300 From: Vladislav Bolkhovitin <vst@...b.net> To: James Bottomley <James.Bottomley@...senPartnership.com> CC: Bart Van Assche <bart.vanassche@...il.com>, Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org>, FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>, linux-scsi@...r.kernel.org, scst-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: Re: Integration of SCST in the mainstream Linux kernel James Bottomley wrote: >>Vladislav Bolkhovitin wrote: >>So, James, what is your opinion on the above? Or the overall SCSI target >>project simplicity doesn't matter much for you and you think it's fine >>to duplicate Linux page cache in the user space to keep the in-kernel >>part of the project as small as possible? > > > The answers were pretty much contained here > > http://marc.info/?l=linux-scsi&m=120164008302435 > > and here: > > http://marc.info/?l=linux-scsi&m=120171067107293 > > Weren't they? No, sorry, it doesn't look so for me. They are about performance, but I'm asking about the overall project's architecture, namely about one part of it: simplicity. Particularly, what do you think about duplicating Linux page cache in the user space to have zero-copy cached I/O? Or can you suggest another architectural solution for that problem in the STGT's approach? Vlad -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists