From: Mike Snitzer <snitzer@redhat.com>
To: agk@redhat.com
Cc: dm-devel@redhat.com, "Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: expose dm-stripe target's topology I/O hints
Date: Wed, 5 Aug 2009 09:07:51 -0400 [thread overview]
Message-ID: <20090805130751.GA20921@redhat.com> (raw)
In-Reply-To: <1247261592-9803-1-git-send-email-snitzer@redhat.com>
On Fri, Jul 10 2009 at 5:33pm -0400,
Mike Snitzer <snitzer@redhat.com> wrote:
> Add .io_hints to 'struct target_type' to allow the I/O hints portion of
> the 'struct queue_limits' to be set by each target. Expose dm-stripe
> target's topology I/O hints.
>
> NOTE: This patch makes use of blk_limits_io_min(); which will be
> upstream, via the block tree, in the near future.
Linus has pulled in the block changes that this patch depends on; see
linux-2.6 commits:
7c958e32649e0c35801762878fb0b6da8c55a515
70dd5bf3b99964d52862ad2810c24cc32a553535
So this .io_hints patch is good to go upstream now.
Mike
next prev parent reply other threads:[~2009-08-05 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 21:33 [PATCH] expose dm-stripe target's topology I/O hints Mike Snitzer
2009-08-05 13:07 ` Mike Snitzer [this message]
2009-08-21 14:16 ` Mike Snitzer
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=20090805130751.GA20921@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.