[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071220.163058.185565456.davem@davemloft.net>
Date: Thu, 20 Dec 2007 16:30:58 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: rusty@...tcorp.com.au
Cc: fujita.tomonori@....ntt.co.jp, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org, jens.axboe@...cle.com,
dougg@...que.net
Subject: Re: [PATCH 0/5] sg_ring for scsi
From: Rusty Russell <rusty@...tcorp.com.au>
Date: Fri, 21 Dec 2007 10:13:38 +1100
> But, as demonstrated, there are real benefits of having an explicit header:
>
> 1) It removes the chain-end/explicit count ambiguity (see
> http://lkml.org/lkml/2007/10/25/209 & thread)
> 2) It allows others to manipulate sg chains, which couldn't be done before
> (eg. the ATA code which wants to append a padding element).
> 3) I can now hand you an sg ring for you to fill: sg chains can't do that.
>
> In short, sg_ring is generally useful primitive. sg chains are a clever hack
> for scsi_lib to create, and everyone else to read.
I do not refute any of this :-)
--
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