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: Sat, 19 Jul 2008 09:59:11 +0900 From: Tejun Heo <htejun@...il.com> To: Pierre Ossman <drzeus@...eus.cx> CC: "Rafael J. Wysocki" <rjw@...k.pl>, James Bottomley <James.Bottomley@...senpartnership.com>, Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, Kernel Testers List <kernel-testers@...r.kernel.org>, scsi <linux-scsi@...r.kernel.org>, Jens Axboe <jens.axboe@...cle.com>, linux-ide <linux-ide@...r.kernel.org>, Jeff Garzik <jeff@...zik.org>, Takashi Iwai <tiwai@...e.de>, tino.keitel@....de Subject: Re: linux-next: Tree for July 16 (crash on quad core AMD) Pierre Ossman wrote: > I just have one objection to your version, and that is that it cannot > be used to nibble away at the sg list. The _next() call jumps an entire > page, whereas you sometimes need to consume that page in two different > sweeps. This could be handled by some external buffer that keeps the > remainder of the page, but the point of these functions was to keep > things simple for the callers. Well, I don't know how often such usages would be necessary. If it's a very common ops, you can add a param to the next function but frankly I think it's better to build a inside control structure for that. There's no need for external buffer, just an inner loop is sufficient. -- tejun -- 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