From: Philipp Reisner <philipp.reisner@linbit.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, drbd-dev@lists.linbit.com
Subject: Re: [GIT PULL] drbd-8.3 updates
Date: Wed, 03 Oct 2012 15:49:13 +0200 [thread overview]
Message-ID: <1646250.CkOtqoMF8x@fat-tyre> (raw)
In-Reply-To: <506C343E.60203@kernel.dk>
> Thanks, one question before this is pulled in:
> > Philipp Reisner (6):
> > drbd: Add a drbd directory to sysfs
> > drbd: expose the data generation identifiers via sysfs
>
> What are these? It's sitting in /sys/block/<dev>/drbd/, I don't see any
> documentation or justification for that.
>
> Why isn't it off in debugfs or similar instead?
The long-time goal is to get rid of the /proc/drbd virtual file, and
present the information that was there in a more structured way in /sys.
This patch adds a very first step into that direction. Later we intend to
have here things like the connections state, device roles, statistics
counters there.
When coming up with the layout we used the sysfs presence of software raid
as example.
I have removed it from this pull-request, so that there is more time for
consideration before the next merge window.
The following changes since commit fab74e7a8f0f8d0af2356c28aa60d55f9e6f5f8b:
loop: Make explicit loop device destruction lazy (2012-09-28 10:42:23 +0200)
are available in the git repository at:
git://git.drbd.org/linux-drbd.git for-jens
for you to fetch changes up to 56a2dabd4d953b70c4630387368d79d6d1625c1d:
drbd: log request sector offset and size for IO errors (2012-10-03 15:46:04 +0200)
----------------------------------------------------------------
Lars Ellenberg (8):
drbd: introduce stop-sector to online verify
drbd: panic on delayed completion of aborted requests
drbd: fix potential deadlock during bitmap (re-)allocation
drbd: a few more GFP_KERNEL -> GFP_NOIO
drbd: wait for meta data IO completion even with failed disk, unless force-detached
drbd: prepare for more than 32 bit flags
drbd: always write bitmap on detach
drbd: log request sector offset and size for IO errors
Philipp Reisner (4):
drbd: Protect accesses to the uuid set with a spinlock
drbd: Fix a potential issue with the DISCARD_CONCURRENT flag
drbd: Avoid NetworkFailure state during disconnect
drbd: Remove dead code
drivers/block/drbd/drbd_actlog.c | 19 ++--
drivers/block/drbd/drbd_bitmap.c | 24 ++---
drivers/block/drbd/drbd_int.h | 108 +++++++++++++++++------
drivers/block/drbd/drbd_main.c | 170 ++++++++++++++++++++++++------------
drivers/block/drbd/drbd_nl.c | 74 +++++++++-------
drivers/block/drbd/drbd_proc.c | 14 ++-
drivers/block/drbd/drbd_receiver.c | 147 ++++++++++++++++---------------
drivers/block/drbd/drbd_req.c | 43 ++++++---
drivers/block/drbd/drbd_worker.c | 87 ++++++++++++++----
include/linux/drbd.h | 4 +-
include/linux/drbd_nl.h | 1 +
11 files changed, 451 insertions(+), 240 deletions(-)
Best,
Phil
next prev parent reply other threads:[~2012-10-03 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 13:02 Philipp Reisner
2012-10-03 6:44 ` Jens Axboe
2012-10-03 9:24 ` Philipp Reisner
2012-10-03 10:07 ` Philipp Reisner
2012-10-03 12:49 ` Jens Axboe
2012-10-03 13:49 ` Philipp Reisner [this message]
2012-10-03 14:04 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2012-05-10 12:19 Philipp Reisner
2012-05-18 14:22 ` Jens Axboe
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=1646250.CkOtqoMF8x@fat-tyre \
--to=philipp.reisner@linbit.com \
--cc=axboe@kernel.dk \
--cc=drbd-dev@lists.linbit.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
all inboxes | Powered by JetHome®