From: Jens Axboe <jens.axboe@oracle.com>
To: Benny Halevy <bhalevy@panasas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/13] i386 sg: add support for chaining scatterlists
Date: Thu, 10 May 2007 13:23:55 +0200 [thread overview]
Message-ID: <20070510112355.GQ4629@kernel.dk> (raw)
In-Reply-To: <4642FB1B.80702@panasas.com>
On Thu, May 10 2007, Benny Halevy wrote:
> Jens Axboe wrote:
> > +#define sg_is_chain(sg) ((unsigned long) (sg)->page & 0x01)
> > +#define sg_chain_ptr(sg) \
> > + ((struct scatterlist *) ((unsigned long) (sg)->page & ~0x01))
> > +
> > +/*
> > + * We overload the meaning of ->page for sg chaining. If the LSB is
> > + * set, the page member contains a pointer to the next sgtable.
> > + */
> > +static inline struct scatterlist *sg_next(struct scatterlist *sg)
> > +{
> > + if (sg_is_chain(sg))
> > + return sg_chain_ptr(sg);
> > +
> > + return sg + 1;
> > +}
>
> Jens, should sg_next ever return the sg containing the chain link?
> If sg points at the entry right before the link entry, don't we
> want to skip it?
>
> E.g.:
>
> static inline struct scatterlist *sg_next(struct scatterlist *sg)
> {
> struct scatterlist *next;
>
> /* just in case, shouldn't really ever be here */
> if (sg_is_chain(sg))
> return sg_chain_ptr(sg);
>
> next = sg + 1;
>
> if (sg_is_chain(next))
> return sg_chain_ptr(next);
>
> return next;
> }
You are right, I got that mixed up, I changed the setup to overloading
->page right before posting it. So:
static inline struct scatterlist *sg_next(struct scatterlist *sg)
{
sg++;
if (unlikely(sg_is_chain(sg)))
sg = sg_chain_ptr(sg);
return sg;
}
--
Jens Axboe
next prev parent reply other threads:[~2007-05-10 11:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 10:21 [PATCH 0/13] Chaining sg lists for bio IO commands v3 Jens Axboe
2007-05-10 10:21 ` [PATCH 1/13] crypto: don't pollute the global namespace with sg_next() Jens Axboe
2007-05-10 10:21 ` [PATCH 2/13] Add sg helpers for iterating over a scatterlist table Jens Axboe
2007-05-10 10:39 ` Andrew Morton
2007-05-10 10:42 ` Jens Axboe
2007-05-10 10:21 ` [PATCH 3/13] libata: convert to using sg helpers Jens Axboe
2007-05-10 10:21 ` [PATCH 4/13] block: " Jens Axboe
2007-05-10 10:21 ` [PATCH 5/13] scsi: " Jens Axboe
2007-05-10 10:21 ` [PATCH 6/13] i386 dma_map_sg: " Jens Axboe
2007-05-10 10:21 ` [PATCH 7/13] i386 sg: add support for chaining scatterlists Jens Axboe
2007-05-10 10:43 ` Andrew Morton
2007-05-10 10:44 ` Jens Axboe
2007-05-10 10:46 ` Jens Axboe
2007-05-10 10:52 ` Andrew Morton
2007-05-10 11:21 ` Jens Axboe
2007-05-10 10:59 ` Benny Halevy
2007-05-10 11:23 ` Jens Axboe [this message]
2007-05-10 10:21 ` [PATCH 8/13] x86-64: update iommu/dma mapping functions to sg helpers Jens Axboe
2007-05-10 10:21 ` [PATCH 9/13] [PATCH] x86-64: enable sg chaining Jens Axboe
2007-05-10 10:21 ` [PATCH 10/13] scsi: simplify scsi_free_sgtable() Jens Axboe
2007-05-10 10:21 ` [PATCH 11/13] SCSI: support for allocating large scatterlists Jens Axboe
2007-05-10 10:48 ` Andrew Morton
2007-05-10 10:52 ` Jens Axboe
2007-05-10 12:38 ` Alan Cox
2007-05-10 10:21 ` [PATCH 12/13] ll_rw_blk: temporarily enable max_segments tweaking Jens Axboe
2007-05-10 10:49 ` Andrew Morton
2007-05-10 11:20 ` Jens Axboe
2007-05-10 10:21 ` [PATCH 13/13] scsi drivers: sg chaining Jens Axboe
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=20070510112355.GQ4629@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=bhalevy@panasas.com \
--cc=linux-kernel@vger.kernel.org \
/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