public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: zkabelac@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW_DM man/dmsetup.8.in
Date: Mon, 09 Jan 2012 12:28:00 -0000	[thread overview]
Message-ID: <20120109122848.30047.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	zkabelac@sourceware.org	2012-01-09 12:28:47

Modified files:
	.              : WHATS_NEW_DM 
	man            : dmsetup.8.in 

Log message:
	Improve readahead in dmsetup man page

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW_DM.diff?cvsroot=lvm2&r1=1.527&r2=1.528
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/dmsetup.8.in.diff?cvsroot=lvm2&r1=1.47&r2=1.48

--- LVM2/WHATS_NEW_DM	2012/01/09 12:26:14	1.527
+++ LVM2/WHATS_NEW_DM	2012/01/09 12:28:47	1.528
@@ -1,5 +1,6 @@
 Version 1.02.68 -
 ==================================
+  Improve dmsetup man page about readahead parameter.
   Use sysfs to set/get of read-ahead setting if possible.
   Fix lvm2-monitor init script to use normalized output when using vgs.
   Add test for max length (DM_MAX_TYPE_NAME) of target type name.
--- LVM2/man/dmsetup.8.in	2011/11/30 22:32:37	1.47
+++ LVM2/man/dmsetup.8.in	2012/01/09 12:28:47	1.48
@@ -15,6 +15,8 @@
 .RS
 .IR table_file ]
 .RB [{ \-\-addnodeoncreate | \-\-addnodeonresume }]
+.RB [ \-\-readahead
+.RI [ \+ ]< sectors >| auto | none ]
 .RE
 .br
 .B dmsetup deps
@@ -85,6 +87,10 @@
 .B dmsetup resume
 .I device_name
 .RB [{ \-\-addnodeoncreate | \-\-addnodeonresume }]
+.RS
+.RB [ \-\-readahead
+.RI [ \+ ]< sectors >| auto | none ]
+.RE
 .br
 .B dmsetup setgeometry
 .I device_name cyl head sect start
@@ -202,11 +208,11 @@
 .TP
 .IR \fB\-\-readahead \ [ \+ ]< sectors >| auto | none
 Specify read ahead size in units of sectors.
-The default value is "auto" which allows the kernel to choose
-a suitable value automatically.  The + prefix lets you
+The default value is \fIauto\fP which allows the kernel to choose
+a suitable value automatically.  The \fI\+\fP prefix lets you
 specify a minimum value which will not be used if it is
 smaller than the value chosen by the kernel.
-"None" is equivalent to specifying zero.
+The value \fInone\fP is equivalent to specifying zero.
 .TP
 .BR \-r | \-\-readonly
 Set the table being loaded read-only.
@@ -248,6 +254,8 @@
 .RB [ \-\-notable | \-\-table
 .RI < \fItable >| table_file ]
 .RB [{ \-\-addnodeoncreate | \-\-addnodeonresume }]
+.RB [ \-\-readahead
+.RI [ + ]< sectors >| auto | none ]
 .br
 Creates a device with the given name.
 If table_file or <table> is supplied, the table is loaded and made live.
@@ -402,6 +410,8 @@
 .B resume
 .I device_name
 .RB [{ \-\-addnodeoncreate | \-\-addnodeonresume }]
+.RB [ \-\-readahead
+.RI [ + ]< sectors >| auto | none ]
 .br
 Un-suspends a device.
 If an inactive table has been loaded, it becomes live.


             reply	other threads:[~2012-01-09 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 12:28 zkabelac [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-12 22:48 zkabelac
2011-09-23  9:51 zkabelac
2010-03-08 16:04 mbroz

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=20120109122848.30047.qmail@sourceware.org \
    --to=zkabelac@sourceware.org \
    --cc=lvm-devel@redhat.com \
    --cc=lvm2-cvs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).