mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: Jens Axboe <jens.axboe@oracle.com>
Subject: [PATCH 6/19] Add chained sg support to linux/scatterlist.h
Date: Wed, 16 May 2007 10:32:20 +0200	[thread overview]
Message-ID: <1179304354561-git-send-email-jens.axboe@oracle.com> (raw)
In-Reply-To: <11793043533744-git-send-email-jens.axboe@oracle.com>

The core of the patch - allow the last sg element in a scatterlist
table to point to the start of a new table. We overload the LSB of
the page pointer to indicate whether this is a valid sg entry, or
merely a link to the next list.

Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
---
 include/linux/scatterlist.h |   79 +++++++++++++++++++++++++++++++++++++++++-
 1 files changed, 77 insertions(+), 2 deletions(-)

diff --git a/include/linux/scatterlist.h b/include/linux/scatterlist.h
index bed5ab4..10f6223 100644
--- a/include/linux/scatterlist.h
+++ b/include/linux/scatterlist.h
@@ -20,8 +20,36 @@ static inline void sg_init_one(struct scatterlist *sg, const void *buf,
 	sg_set_buf(sg, buf, buflen);
 }
 
-#define sg_next(sg)		((sg) + 1)
-#define sg_last(sg, nents)	(&(sg[(nents) - 1]))
+/*
+ * We overload the LSB of the page pointer to indicate whether it's
+ * a valid sg entry, or whether it points to the start of a new scatterlist.
+ * Those low bits are there for everyone! (thanks mason :-)
+ */
+#define sg_is_chain(sg)		((unsigned long) (sg)->page & 0x01)
+#define sg_chain_ptr(sg)	\
+	((struct scatterlist *) ((unsigned long) (sg)->page & ~0x01))
+
+/**
+ * sg_next - return the next scatterlist entry in a list
+ * @sg:		The current sg entry
+ *
+ * Usually the next entry will be @sg@ + 1, but if this sg element is part
+ * of a chained scatterlist, it could jump to the start of a new
+ * scatterlist array.
+ *
+ * Note that the caller must ensure that there are further entries after
+ * the current entry, this function will NOT return NULL for an end-of-list.
+ *
+ */
+static inline struct scatterlist *sg_next(struct scatterlist *sg)
+{
+	sg++;
+
+	if (unlikely(sg_is_chain(sg)))
+		sg = sg_chain_ptr(sg);
+
+	return sg;
+}
 
 /*
  * Loop over each sg element, following the pointer to a new list if necessary
@@ -29,4 +57,51 @@ static inline void sg_init_one(struct scatterlist *sg, const void *buf,
 #define for_each_sg(sglist, sg, nr, __i)	\
 	for (__i = 0, sg = (sglist); __i < (nr); __i++, sg = sg_next(sg))
 
+/**
+ * sg_last - return the last scatterlist entry in a list
+ * @sgl:	First entry in the scatterlist
+ * @nents:	Number of entries in the scatterlist
+ *
+ * Should only be used casually, it (currently) scan the entire list
+ * to get the last entry.
+ *
+ * Note that the @sgl@ pointer passed in need not be the first one,
+ * the important bit is that @nents@ denotes the number of entries that
+ * exist from @sgl@.
+ *
+ */
+static inline struct scatterlist *sg_last(struct scatterlist *sgl,
+					  unsigned int nents)
+{
+#ifdef ARCH_HAS_SG_CHAIN
+	struct scatterlist *ret = &sgl[nents - 1];
+#else
+	struct scatterlist *sg, *ret = NULL;
+	int i;
+
+	for_each_sg(sgl, sg, nents, i)
+		ret = sg;
+
+#endif
+	return ret;
+}
+
+/**
+ * sg_chain - Chain two sglists together
+ * @prv:	First scatterlist
+ * @prv_nents:	Number of entries in prv
+ * @sgl:	Second scatterlist
+ *
+ * Links @prv@ and @sgl@ together, to form a longer scatterlist.
+ *
+ */
+static inline void sg_chain(struct scatterlist *prv, unsigned int prv_nents,
+			    struct scatterlist *sgl)
+{
+#ifndef ARCH_HAS_SG_CHAIN
+	BUG();
+#endif
+	prv[prv_nents - 1].page = (struct page *) ((unsigned long) sgl | 0x01);
+}
+
 #endif /* _LINUX_SCATTERLIST_H */
-- 
1.5.2.rc1


  parent reply	other threads:[~2007-05-16  8:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16  8:32 [PATCH 0/19] Chaining sg lists for big IO commands v6 Jens Axboe
2007-05-16  8:32 ` [PATCH 1/19] crypto: don't pollute the global namespace with sg_next() Jens Axboe
2007-05-16  8:32 ` [PATCH 2/19] Add sg helpers for iterating over a scatterlist table Jens Axboe
2007-05-16  8:32 ` [PATCH 3/19] libata: convert to using sg helpers Jens Axboe
2007-05-16  8:32 ` [PATCH 4/19] block: " Jens Axboe
2007-05-16  8:32 ` [PATCH 5/19] scsi: " Jens Axboe
2007-05-16 11:17   ` Cornelia Huck
2007-05-16 11:25     ` Jens Axboe
2007-05-16  8:32 ` Jens Axboe [this message]
2007-05-16  8:32 ` [PATCH 7/19] i386 dma_map_sg: " Jens Axboe
2007-05-16  8:32 ` [PATCH 8/19] i386: enable sg chaining Jens Axboe
2007-05-16  8:32 ` [PATCH 9/19] swiotlb: sg chaining support Jens Axboe
2007-05-16  8:32 ` [PATCH 10/19] x86-64: update iommu/dma mapping functions to sg helpers Jens Axboe
2007-05-16  8:32 ` [PATCH 11/19] x86-64: enable sg chaining Jens Axboe
2007-05-16  8:32 ` [PATCH 12/19] IA64: sg chaining support Jens Axboe
2007-05-16  8:32 ` [PATCH 13/19] PPC: " Jens Axboe
2007-05-16  8:32 ` [PATCH 14/19] SPARC: " Jens Axboe
2007-05-16  8:32 ` [PATCH 15/19] SPARC64: " Jens Axboe
2007-05-16  8:32 ` [PATCH 16/19] scsi: simplify scsi_free_sgtable() Jens Axboe
2007-05-16  8:32 ` [PATCH 17/19] SCSI: support for allocating large scatterlists Jens Axboe
2007-05-16  8:32 ` [PATCH 18/19] ll_rw_blk: temporarily enable max_segments tweaking Jens Axboe
2007-05-16  8:32 ` [PATCH 19/19] drivers: sg chaining support 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=1179304354561-git-send-email-jens.axboe@oracle.com \
    --to=jens.axboe@oracle.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

Powered by JetHome