linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Vesely <jvesely@redhat.com>
To: Jens Axboe <axboe@kernel.dk>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	linux-kernel@vger.kernel.org
Cc: Kent Overstreet <koverstreet@google.com>,
	Rob Evers <revers@redhat.com>, Tomas Henzl <thenzl@redhat.com>,
	Nikola Pajkovsky <npajkovs@redhat.com>,
	Kai Makisara <Kai.Makisara@kolumbus.fi>,
	linux-scsi@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Don Howard <dhoward@redhat.com>
Subject: [PATCH v4 0/2] block: Allow merging of tail pages into the last segment
Date: Fri, 12 Jul 2013 17:52:21 +0200	[thread overview]
Message-ID: <1373644343-6671-1-git-send-email-jvesely@redhat.com> (raw)

Hi

These patches modify __bio_add_page to accept pages that extent the last bio
segment. some drivers craft their buffers and rely on this behavior (see
message in patch 2 for details)


jan

v4: whitespace fixes to make checkpatch happy

v3: Use code from __blk_recalc_rq_segments to decide whether the page is
    mergeable, 

v2: modify a comment



             reply	other threads:[~2013-07-12 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12 15:52 Jan Vesely [this message]
2013-07-12 15:52 ` [PATCH v4 1/2] block: factor out vector mergeable decision to a helper function Jan Vesely
2013-07-12 15:52 ` [PATCH v4 2/2] block: modify __bio_add_page check to accept pages that don't start a new segment Jan Vesely
2013-07-26 10:41 ` [PATCH v4 0/2] block: Fix regression since 46081b166415acb66d4b3150ecefcd9460bb48a1 (was: Allow merging of tail pages into the last segment) Jan Vesely

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=1373644343-6671-1-git-send-email-jvesely@redhat.com \
    --to=jvesely@redhat.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=Kai.Makisara@kolumbus.fi \
    --cc=axboe@kernel.dk \
    --cc=dhoward@redhat.com \
    --cc=koverstreet@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=npajkovs@redhat.com \
    --cc=revers@redhat.com \
    --cc=thenzl@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    /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 NNTP newsgroup(s).