From: Tejun Heo <htejun@gmail.com>
To: Pierre Ossman <drzeus@drzeus.cx>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
scsi <linux-scsi@vger.kernel.org>,
Jens Axboe <jens.axboe@oracle.com>,
linux-ide <linux-ide@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>, Takashi Iwai <tiwai@suse.de>,
tino.keitel@gmx.de
Subject: Re: linux-next: Tree for July 16 (crash on quad core AMD)
Date: Sat, 19 Jul 2008 09:59:11 +0900 [thread overview]
Message-ID: <48813C5F.70007@gmail.com> (raw)
In-Reply-To: <20080719004736.626ef169@mjolnir.drzeus.cx>
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
next prev parent reply other threads:[~2008-07-19 0:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080716235011.ac9643aa.sfr@canb.auug.org.au>
2008-07-16 22:53 ` linux-next: Tree for July 16 (crash on quad core AMD) Rafael J. Wysocki
2008-07-16 23:01 ` James Bottomley
[not found] ` <1216249292.3358.66.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-07-16 23:09 ` Rafael J. Wysocki
2008-07-18 12:38 ` Tejun Heo
[not found] ` <48808EE0.2060603-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-07-18 22:47 ` Pierre Ossman
2008-07-19 0:59 ` Tejun Heo [this message]
2008-07-19 1:30 ` Pierre Ossman
[not found] ` <20080719033050.552f9b49-OhHrUh4vRMSnewYJFaQfwJ5kstrrjoWp@public.gmane.org>
2008-07-19 2:12 ` Tejun Heo
2008-07-19 12:07 ` Pierre Ossman
2008-07-19 14:03 ` Tejun Heo
2008-07-20 22:40 ` Pierre Ossman
[not found] ` <20080721004033.1fc66aa3-OhHrUh4vRMSnewYJFaQfwJ5kstrrjoWp@public.gmane.org>
2008-07-21 0:38 ` Tejun Heo
[not found] ` <4883DA8C.5030306-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-07-21 11:32 ` Pierre Ossman
2008-07-21 15:35 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48813C5F.70007@gmail.com \
--to=htejun@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=drzeus@drzeus.cx \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sfr@canb.auug.org.au \
--cc=tino.keitel@gmx.de \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).