public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Christoph Hellwig <hch@lst.de>
Cc: James Bottomley <James.Bottomley@suse.de>,
	Mike Snitzer <snitzer@redhat.com>,
	axboe@kernel.dk, dm-devel@redhat.com,
	linux-kernel@vger.kernel.org, martin.petersen@oracle.com,
	akpm@linux-foundation.org, linux-scsi@vger.kernel.org,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Subject: Re: [PATCH 1/2] block: fix leaks associated with discard request payload
Date: Wed, 30 Jun 2010 13:25:01 +0300	[thread overview]
Message-ID: <4C2B1B7D.2090607@panasas.com> (raw)
In-Reply-To: <20100630084204.GA27609@lst.de>

On 06/30/2010 11:42 AM, Christoph Hellwig wrote:
> On Wed, Jun 30, 2010 at 11:32:43AM +0300, Boaz Harrosh wrote:
>> May I ask a silly question? Why the dynamic allocation?
>>
>> Why not have a const-static single global page at the block-layer somewhere
>> that will be used for all discard-type operations and be done with it once and
>> for all. A single page can be used for any size bio , any number of concurrent
>> discards, any ZERO needed operation. It can also be used by other operations
>> like padding and others. In fact isn't there one for the libsata padding?
> 
> for UNMAP we need to write into the payload.  And for ATA TRIM we need
> to write into the WRITE SAME payload.  

OK, Thanks, I see. Is it one of these operations, (like we have in OSD) where
the CDB information spills into the payload? like the scatter-gather and extent
lists and such. Do we actually use a WRITE_SAME which is not zero? for what use?

> That's another layering violation
> for those looking for them, btw..
> 

Agreed

  reply	other threads:[~2010-06-30 10:25 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100622180029.GA15950@redhat.com>
     [not found] ` <1277582211-10725-1-git-send-email-snitzer@redhat.com>
2010-06-27 15:29   ` [PATCH 1/2] block: fix leaks associated with discard request payload James Bottomley
2010-06-28 17:16     ` Martin K. Petersen
2010-06-29  8:00       ` Boaz Harrosh
2010-06-29 22:28     ` [dm-devel] " Mikulas Patocka
2010-06-29 23:03       ` James Bottomley
2010-06-29 23:51         ` Mike Snitzer
2010-06-30  0:11         ` [dm-devel] " Mikulas Patocka
2010-06-30 14:22           ` James Bottomley
2010-06-30 15:36             ` Mike Snitzer
2010-06-30 16:26               ` James Bottomley
2010-07-01 12:28             ` [dm-devel] " Mikulas Patocka
2010-07-01 12:46               ` Mike Snitzer
2010-07-01 14:03                 ` Mikulas Patocka
2010-07-01 12:49               ` [dm-devel] " Alasdair G Kergon
2010-06-30  8:32     ` Boaz Harrosh
2010-06-30  8:42       ` Christoph Hellwig
2010-06-30 10:25         ` Boaz Harrosh [this message]
2010-06-30 10:41           ` Christoph Hellwig
2010-06-30 10:57             ` Boaz Harrosh
2010-06-30 12:18               ` Mike Snitzer
     [not found] <20100627174721D.fujita.tomonori@lab.ntt.co.jp>
     [not found] ` <20100627092652.GA11625@lst.de>
     [not found]   ` <20100627185927K.fujita.tomonori@lab.ntt.co.jp>
2010-06-27 10:35     ` FUJITA Tomonori
2010-06-27 11:07       ` Christoph Hellwig
2010-06-27 12:32         ` FUJITA Tomonori
2010-06-27 14:16           ` Mike Snitzer
2010-06-27 15:35             ` Christoph Hellwig
2010-06-27 16:23               ` FUJITA Tomonori
2010-06-27 15:33           ` Christoph Hellwig
2010-06-28  7:57           ` Christoph Hellwig
2010-06-28  8:14             ` FUJITA Tomonori
2010-06-28  8:18               ` Jens Axboe
2010-06-28  8:45                 ` FUJITA Tomonori
2010-06-28 15:25               ` Christoph Hellwig
2010-06-30 11:55                 ` FUJITA Tomonori
2010-07-01  4:21                   ` FUJITA Tomonori

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=4C2B1B7D.2090607@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=snitzer@redhat.com \
    /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