5:35 AM Palmer Dabbelt wrote:
> On Tue, 15 Dec 2020 22:17:06 PST (-0800), ruby.w...@gmail.com wrote:
> > Hi my name is Akira Hayakawa. I am maintaining an out-of-tree DM target
> > named dm-writeboost.
> >
> > Sorry to step in. But this is a very interesting topic at
Hi my name is Akira Hayakawa. I am maintaining an out-of-tree DM target
named dm-writeboost.
Sorry to step in. But this is a very interesting topic at least to me.
I have been looking for something like dm-user because I believe we should
be able to implement virtual block devices in Rust
Hi Jonas,
I am developing dm-writeboost. Thank you for your interest.
I couldn't understand how you try to stack devices.
You should share diagram if you want others to know your idea precisely.
But this may help you. dm-writeboost can't use zram as the caching device.
I thought this is device-m
Hi,
I found an interesting behavior when I was debugging my dm-writeboost.
device-mapper splits in-coming bio into small bios called clone bio and
target writes "how to handle a clone bio". There is end_io method which is
called in clone_endio. That should be called when the clone bio is acked
by
Hi Peter,
Just curious.
Are you looking for device-mapper in userland like FUSE?
Akira
On 2016/08/04 6:46, Peter Desnoyers wrote:
> We’re developing an SMR translation layer in a device mapper target, and we’d
> like to keep a lot of the complexity (recovery at startup, parts of the
> garbage
as introduced it caused READ bios to
> no longer be errored with -EIO during the down_interval. This had to do
> with the complexity of needing to submit READs if the corrupt_bio_byte
> feature was used.
>
> Fix it so READ bios are properly errored with -EIO; doing so e
with -EIO during the down_interval. This had to do
> with the complexity of needing to submit READs if the corrupt_bio_byte
> feature was used.
>
> Fix it so READ bios are properly errored with -EIO; doing so early in
> flakey_map() as long as there isn't a match fo
:
> Hi Akira,
> Sorry I was on holiday.
> I have patch ready, would you be able to test it before posting it.
>
> Let me know if I should build the kernel for you or just share the source
> with you.
>
> Lukas
>
> On Sun, Jul 17, 2016 at 3:36 AM, Akira Hayakawa wrote:
> On 2016/07/06 18:52, Lukas Herbolt wrote:
>> Hi,
>> Yes this part is wrong and reads are not dropped.
>> I have a patch ready, just have to send it out.
btw, is this fix going to be included in the next release?
On 2016/07/06 21:54, Akira Hayakawa wrote:
> Thanks,
>
ding 0
- Akira
On 2016/07/06 18:52, Lukas Herbolt wrote:
> Hi,
> Yes this part is wrong and reads are not dropped.
> I have a patch ready, just have to send it out.
>
> Lukas
>
> On Wed, Jul 6, 2016 at 8:33 AM, Akira Hayakawa wrote:
>
>> Hi,
>>
>> I am
Hi,
I am using dm-flakey to emulate a broken device that should return -EIO on both
read and write.
I use the parameter up_interval=0 and down_interval=1.
But when I am dd-ing the flakey device, while write fails, read succeeds.
This isn't the behavior I expect.
Then I looked into the code.
32
Hi,
To test my ssd-caching module dm-writeboost
(https://github.com/akiradeveloper/dm-writeboost)
I used to add tests to forked device-mapper-test-suite but I found that it's
not easy to maintain
the tests because Ruby doesn't give us compile-time type checking and the code
base is bit messy
be
If you don't mind out-of-tree kernel module,
there is dm-writeboost
https://github.com/akiradeveloper/dm-writeboost
it's both read/write caching and especially optimized for
write caching.
If you are using Ubuntu or Debian, it's available in
the packages.
Also, we have management tool that includ
13 matches
Mail list logo
