public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: axboe@kernel.dk, linux-kernel@vger.kernel.org,
	jaxboe@fusionio.com, lidongyang@novell.com, joe.jin@oracle.com
Subject: Re: [GIT PULL] (xen) stable/for-jens-3.2 - blkback and blkfront patches for 3.2
Date: Wed, 21 Sep 2011 11:17:32 -0400	[thread overview]
Message-ID: <20110921151732.GA28043@infradead.org> (raw)
In-Reply-To: <20110921150955.GH541@phenom.oracle.com>

On Wed, Sep 21, 2011 at 11:09:55AM -0400, Konrad Rzeszutek Wilk wrote:
> Hey Jens,
> 
> Please pull the following git tree in your 3.2 drivers tree:
> 
>  git pull git://oss.oracle.com/git/kwilk/xen.git stable/for-jens-3.2
> 
> which has an exciting new feature - the discard ('feature-discard')
> aka TRIM/UNMAP. Now they can be passed from the guest to the backend.

What is the design of them?  Do you provide the 'discard zeroes data'
flag (mandatory for any kind of relible operation) and 'discard
granularity / alignment' tunables (very useful)?


  reply	other threads:[~2011-09-21 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 15:09 [GIT PULL] (xen) stable/for-jens-3.2 - blkback and blkfront patches for 3.2 Konrad Rzeszutek Wilk
2011-09-21 15:17 ` Christoph Hellwig [this message]
2011-09-21 15:35   ` Konrad Rzeszutek Wilk
     [not found]     ` <CAKH3R4_yAhmRE3Lg73gE3iKD_Dcp0u_hr8rHekSyRJVQ02KbGw@mail.gmail.com>
2011-09-22 15:54       ` Konrad Rzeszutek Wilk
     [not found]         ` <CAKH3R4_nMX6MTpwfy92FGRu+1bO1ck4_0Qd812Tnu+hS+v0qdA@mail.gmail.com>
2011-09-25  2:37           ` Li Dongyang
  -- strict thread matches above, loose matches on Subject: below --
2011-10-13 15:21 Konrad Rzeszutek Wilk
2011-10-14 16:59 ` Konrad Rzeszutek Wilk

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=20110921151732.GA28043@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=jaxboe@fusionio.com \
    --cc=joe.jin@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=lidongyang@novell.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