[take8 1/4] dst: Distributed storage documentation.

Distributed storage documentation. Algorithms used in the system, userspace interfaces (sysfs dirs and files), design and implementation details are described here. Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]> diff --git a/Documentation/dst/algorithms.txt b/Documentati

[take8 0/4] dst: Distributed storage.

-by: Evgeniy Polyakov [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[take8 4/4] dst: Algorithms used in distributed storage.

Algorithms used in distributed storage. Mirror and linear mapping code. Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] diff --git a/drivers/block/dst/alg_linear.c b/drivers/block/dst/alg_linear.c new file mode 100644 index 000..cb77b57 --- /dev/null +++ b/drivers/block/dst/alg_linear.c

[take8 3/4] dst: Network state machine.

Network state machine. Includes network async processing state machine and related tasks. Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] diff --git a/drivers/block/dst/kst.c b/drivers/block/dst/kst.c new file mode 100644 index 000..ba5e5ef --- /dev/null +++ b/drivers/block/dst/kst.c

[take8 2/4] dst: Core distributed storage files.

Core distributed storage files. Include userspace interfaces, initialization, block layer bindings and other core functionality. Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig index b4c8319..ca6592d 100644 --- a/drivers/block

[take8 1/4] dst: Distributed storage documentation.

Distributed storage documentation. Algorithms used in the system, userspace interfaces (sysfs dirs and files), design and implementation details are described here. Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] diff --git a/Documentation/dst/algorithms.txt b/Documentation/dst

Re: [HIFN 00/03]: RNG support v2

itialization > [HIFN]: Add support for using the random number generator Thanks a lot for your patches. Ack for all three. -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Mor

Re: [HIFN 00/03]: RNG support v2

]: Add support for using the random number generator Thanks a lot for your patches. Ack for all three. -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org

Re: [BUG] New Kernel Bugs

2.6.11 bug and weird network problem which is undetectible on other systems). Yes, we suck, but we try to recover :) -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at htt

Re: [BUG] New Kernel Bugs

is undetectible on other systems). Yes, we suck, but we try to recover :) -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ

Re: [PATCH] make ds1wm driver to check ds1wm_platform_data pointer against NULL

find any user of this platform driver in vanilla kernel, so it is hard to say if driver is used properly or not by external modules, and thus this change is very likely valid. -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body o

Re: [PATCH] make ds1wm driver to check ds1wm_platform_data pointer against NULL

, and thus this change is very likely valid. -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org

[3/4] Distributed storage. Algorithms.

Mirror and linear data stripping algorithms for DST. Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]> diff --git a/drivers/block/dst/alg_linear.c b/drivers/block/dst/alg_linear.c new file mode 100644 index 000..cb77b57 --- /dev/null +++ b/drivers/block/dst/alg_linear.c @@ -0,0

[4/4] Distributed storage. Core interfaces.

This one contains core interfaces of the distributed storage, storage and node initialization and cleanup code, block layer callbacks and the like. It also contains Kconfig and Makefile changes. Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]> diff --git a/drivers/block/Kconfig b/d

[2/4] Distributed storage. Network processing.

This file contains all bits needed for async non-blocking network processing of the block requests directed to DST. Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]> diff --git a/drivers/block/dst/kst.c b/drivers/block/dst/kst.c new file mode 100644 index 000..ba5e5ef --- /dev/null

[1/4] Distributed storage. Documentation.

DST documentation. Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]> diff --git a/Documentation/dst/algorithms.txt b/Documentation/dst/algorithms.txt new file mode 100644 index 000..1437a6a --- /dev/null +++ b/Documentation/dst/algorithms.txt @@ -0,0 +1,115 @@ +Each storage by

[0/4] Distributed storage. Squizzed black-out of the dancing back-aching hippo.

://tservice.net.ru/~s0mbre/old/?section=projects=dst Thank you. Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]> -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordo

Re: [PATCH 6/6] W1: fix memset size error

On Mon, Nov 05, 2007 at 10:30:44AM +0800, Li Zefan ([EMAIL PROTECTED]) wrote: > The size arguments passing to memset is wrong. > > Signed-off-by Li Zefan <[EMAIL PROTECTED]> Thanks a lot, patch is obviously correct. ACK. -- Evgeniy Polyakov - To unsubscribe from

Re: [PATCH 6/6] W1: fix memset size error

On Mon, Nov 05, 2007 at 10:30:44AM +0800, Li Zefan ([EMAIL PROTECTED]) wrote: The size arguments passing to memset is wrong. Signed-off-by Li Zefan [EMAIL PROTECTED] Thanks a lot, patch is obviously correct. ACK. -- Evgeniy Polyakov - To unsubscribe from this list: send the line

[0/4] Distributed storage. Squizzed black-out of the dancing back-aching hippo.

://tservice.net.ru/~s0mbre/old/?section=projectsitem=dst Thank you. Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http

[1/4] Distributed storage. Documentation.

DST documentation. Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] diff --git a/Documentation/dst/algorithms.txt b/Documentation/dst/algorithms.txt new file mode 100644 index 000..1437a6a --- /dev/null +++ b/Documentation/dst/algorithms.txt @@ -0,0 +1,115 @@ +Each storage by itself is just

[2/4] Distributed storage. Network processing.

This file contains all bits needed for async non-blocking network processing of the block requests directed to DST. Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] diff --git a/drivers/block/dst/kst.c b/drivers/block/dst/kst.c new file mode 100644 index 000..ba5e5ef --- /dev/null +++ b

[4/4] Distributed storage. Core interfaces.

This one contains core interfaces of the distributed storage, storage and node initialization and cleanup code, block layer callbacks and the like. It also contains Kconfig and Makefile changes. Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] diff --git a/drivers/block/Kconfig b/drivers/block

[3/4] Distributed storage. Algorithms.

Mirror and linear data stripping algorithms for DST. Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] diff --git a/drivers/block/dst/alg_linear.c b/drivers/block/dst/alg_linear.c new file mode 100644 index 000..cb77b57 --- /dev/null +++ b/drivers/block/dst/alg_linear.c @@ -0,0 +1,104

Re: [PATCH 00/33] Swap over NFS -v14

nt to merge this during development phase. I expect to complete it quite soon (it is in testing stage right now) though with new release scheduled this week. It will also include some small features for userspace (hapiness). Memory management is not changed. -- Evgeniy Polyakov - To unsu

Re: [PATCH 00/33] Swap over NFS -v14

(it is in testing stage right now) though with new release scheduled this week. It will also include some small features for userspace (hapiness). Memory management is not changed. -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message

Re: [0/3] Distributed storage. Mirror algo extension for automatic recovery.

r for distributed filesystem, and probably that will require additional features, I have no clean design so far, but right now I have nothing in the pipe to commit to DST. -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a messa

Re: [0/3] Distributed storage. Mirror algo extension for automatic recovery.

additional features, I have no clean design so far, but right now I have nothing in the pipe to commit to DST. -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org

Re: Distributed storage. Move away from char device ioctls.

should also contain enough information about what underlying data is - git does not store that information (tree, blob or whatever) in its keys, since it does not require it. At least that is how I see it to be implemented. Overall I see this new project as a true copy-on-write FS. Thanks. &

Re: Distributed storage. Move away from char device ioctls.

, since it does not require it. At least that is how I see it to be implemented. Overall I see this new project as a true copy-on-write FS. Thanks. Cheers, Kyle Moffett -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message

[3/3] Distributed storage. Documentation and algorithms.

Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]> diff --git a/Documentation/dst/algorithms.txt b/Documentation/dst/algorithms.txt new file mode 100644 index 000..1437a6a --- /dev/null +++ b/Documentation/dst/algorithms.txt @@ -0,0 +1,115 @@ +Each storage by itself is just

[2/3] Distributed storage. Network state machine.

Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]> diff --git a/drivers/block/dst/kst.c b/drivers/block/dst/kst.c new file mode 100644 index 000..b0608c9 --- /dev/null +++ b/drivers/block/dst/kst.c @@ -0,0 +1,1606 @@ +/* + * 2007+ Copyright (c) Evgeniy Polyakov <[EMAIL PROTECTED]

[1/3] Distributed storage. Core files.

Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]> diff --git a/drivers/block/Makefile b/drivers/block/Makefile index dd88e33..fcf042d 100644 --- a/drivers/block/Makefile +++ b/drivers/block/Makefile @@ -29,3 +29,4 @@ obj-$(CONFIG_VIODASD) += viodasd.o obj-$(CONFIG_BLK_D

[0/3] Distributed storage. Mirror algo extension for automatic recovery.

to DST Thank you. Homepage: http://tservice.net.ru/~s0mbre/old/?section=projects=dst Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]> -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL

[0/3] Distributed storage. Mirror algo extension for automatic recovery.

to DST Thank you. Homepage: http://tservice.net.ru/~s0mbre/old/?section=projectsitem=dst Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More

[1/3] Distributed storage. Core files.

Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] diff --git a/drivers/block/Makefile b/drivers/block/Makefile index dd88e33..fcf042d 100644 --- a/drivers/block/Makefile +++ b/drivers/block/Makefile @@ -29,3 +29,4 @@ obj-$(CONFIG_VIODASD) += viodasd.o obj-$(CONFIG_BLK_DEV_SX8

[2/3] Distributed storage. Network state machine.

Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] diff --git a/drivers/block/dst/kst.c b/drivers/block/dst/kst.c new file mode 100644 index 000..b0608c9 --- /dev/null +++ b/drivers/block/dst/kst.c @@ -0,0 +1,1606 @@ +/* + * 2007+ Copyright (c) Evgeniy Polyakov [EMAIL PROTECTED] + * All rights

[3/3] Distributed storage. Documentation and algorithms.

Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] diff --git a/Documentation/dst/algorithms.txt b/Documentation/dst/algorithms.txt new file mode 100644 index 000..1437a6a --- /dev/null +++ b/Documentation/dst/algorithms.txt @@ -0,0 +1,115 @@ +Each storage by itself is just a set of contiguous

Re: Distributed storage. Security attributes and ducumentation update.

without stopping main device node. > > +| DST storate ---| > > storage? Yep, thanks. -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] M

Re: Distributed storage. Security attributes and ducumentation update.

. +| DST storate ---| storage? Yep, thanks. -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read

Re: [PATCH v2] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.

change bit of the core code to allow creating aliases with the same address as main device, so that you would be able to create ':iw' alias during rdma device initialization? If this solution is not acceptible, then I belive your alias change is the way to go. -- Evgeniy Polyakov -

Re: [PATCH v2] iw_cxgb3: Support iwarp-only interfaces to avoid 4-tuple conflicts.

with the same address as main device, so that you would be able to create ':iw' alias during rdma device initialization? If this solution is not acceptible, then I belive your alias change is the way to go. -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux

Re: [ofa-general] Re: [PATCH v2] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.

of *addr... is correct. Come on, do not start a flame war about how parameters into kmalloc should be provided - there are much more serious issues unresolved yes. It does help grepping the code, but if you feel that this is a serious threat, then use your preferred way. -- Evgeniy Poly

Re: [ofa-general] Re: [PATCH v2] iw_cxgb3: Support iwarp-only interfaces to avoid 4-tuple conflicts.

a flame war about how parameters into kmalloc should be provided - there are much more serious issues unresolved yes. It does help grepping the code, but if you feel that this is a serious threat, then use your preferred way. -- Evgeniy Polyakov - To unsubscribe from this list: send the line

Re: [PATCH v2] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.

y) and in other places too. > > > > Do you mean I shouldn't use sizeof *le, but rather sizeof(struct > iwch_listen_entry)? Is that the preferred coding style? Yes, exactly. > >I skipped rdma internals of the patch, since I do not know it enough > >to judge, but

Re: Distributed storage. Move away from char device ioctls.

be rest under the layer of dust I do not care, I like the process of creating, so if it will fail, I just will get new knowledge. :) > Cheers, Andreas > -- > Andreas Dilger > Principal Software Engineer > Cluster File Systems, Inc. -- Evgeniy Polyakov - To unsubscribe from this l

Re: Distributed storage. Move away from char device ioctls.

new knowledge. :) Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http

Re: [PATCH v2] iw_cxgb3: Support iwarp-only interfaces to avoid 4-tuple conflicts.

not care about proper aliases? That would be much better IMO, but the problem is that I cannot create an alias without an actual ip address. Unless we change the core services to allow it. Thanks for reviewing! Steve. -- Evgeniy Polyakov - To unsubscribe from this list: send

Re: Distributed storage. Move away from char device ioctls.

ced from my mail to Jeff, distributed storage was originally part of the overall filesystem design. -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.o

Re: Distributed storage. Move away from char device ioctls.

ome thoughts about distributed filesystem tightly connected to DST > > (far-far planes so far) > > > >Homepage: > >http://tservice.net.ru/~s0mbre/old/?section=projects=dst > > > >Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]> > > My thoughts.

Re: Distributed storage. Move away from char device ioctls.

filesystem tightly connected to DST (far-far planes so far) Homepage: http://tservice.net.ru/~s0mbre/old/?section=projectsitem=dst Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] My thoughts. But first a disclaimer: Perhaps you will recall me as one of the people who really reads all

Re: Distributed storage. Move away from char device ioctls.

storage was originally part of the overall filesystem design. -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ

Re: [PATCH v2] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.

open_rpl(struct t3cdev *t > return CPL_RET_BUF_DONE; > } > > -static int listen_start(struct iwch_listen_ep *ep) > +static int wait_for_reply(struct iwch_ep_common *epc) > +{ > + PDBG("%s ep %p waiting\n", __FUNCTION__, epc); > + wait_event(epc-&g

Re: [ofa-general] InfiniBand/RDMA merge plans for 2.6.24

gt; Jeff, I posted a fix that doesn't do this. No port sharing. The iwarp > device will use its own ip address and subnet to avoid collisions. You > should review the patch when I post v2. Could you please resend it, since I missed it in [EMAIL PROTECTED] -- Evgeniy Polyakov -

Re: [ofa-general] InfiniBand/RDMA merge plans for 2.6.24

that doesn't do this. No port sharing. The iwarp device will use its own ip address and subnet to avoid collisions. You should review the patch when I post v2. Could you please resend it, since I missed it in [EMAIL PROTECTED] -- Evgeniy Polyakov - To unsubscribe from this list: send

Re: [PATCH v2] iw_cxgb3: Support iwarp-only interfaces to avoid 4-tuple conflicts.

interface is added so that admin would not care about proper aliases? -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read

Re: Distributed storage. Security attributes and ducumentation update.

erence counter is increased in higher layer. Right now there is no way to add or remove nodes after array was started, such functionality requires storage tree lock to be taken and RCU can not be used (since it requires sleeping and I did not investigate sleepable RCU for this purpose). So, essentially RCU is not used in DST :) Thanks for review, Paul. -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: Distributed storage. Security attributes and ducumentation update.

was started, such functionality requires storage tree lock to be taken and RCU can not be used (since it requires sleeping and I did not investigate sleepable RCU for this purpose). So, essentially RCU is not used in DST :) Thanks for review, Paul. -- Evgeniy Polyakov - To unsubscribe from

Re: [1/1] Block device throttling [Re: Distributed storage.]

Hi Daniel. On Thu, Aug 30, 2007 at 04:20:35PM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: > On Wednesday 29 August 2007 01:53, Evgeniy Polyakov wrote: > > Then, if of course you will want, which I doubt, you can reread > > previous mails and find that it was point

Re: [1/1] Block device throttling [Re: Distributed storage.]

Hi Daniel. On Thu, Aug 30, 2007 at 04:20:35PM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: On Wednesday 29 August 2007 01:53, Evgeniy Polyakov wrote: Then, if of course you will want, which I doubt, you can reread previous mails and find that it was pointed to that race

Re: [1/1] Block device throttling [Re: Distributed storage.]

On Tue, Aug 28, 2007 at 02:08:04PM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: > On Tuesday 28 August 2007 10:54, Evgeniy Polyakov wrote: > > On Tue, Aug 28, 2007 at 10:27:59AM -0700, Daniel Phillips ([EMAIL > > PROTECTED]) wrote: > > > > We do not care about one

Re: [1/1] Block device throttling [Re: Distributed storage.]

On Tue, Aug 28, 2007 at 02:08:04PM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: On Tuesday 28 August 2007 10:54, Evgeniy Polyakov wrote: On Tue, Aug 28, 2007 at 10:27:59AM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: We do not care about one cpu being able to increase its

Re: [1/1] Block device throttling [Re: Distributed storage.]

requires cloning and alocation/freeing, which itself is much more costly operation than atomic_sub/dec, it can safely host additional operation). -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTE

Re: Distributed storage.

On Fri, Aug 03, 2007 at 09:04:51AM +0400, Manu Abraham ([EMAIL PROTECTED]) wrote: > On 7/31/07, Evgeniy Polyakov <[EMAIL PROTECTED]> wrote: > > > TODO list currently includes following main items: > > * redundancy algorithm (drop me a request of yo

Re: RFC: issues concerning the next NAPI interface

in anything (actually it is what is supposed to be dropped noticebly). -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.ht

Re: [1/1] Block device throttling [Re: Distributed storage.]

On Mon, Aug 27, 2007 at 02:57:37PM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: > Say Evgeniy, something I was curious about but forgot to ask you > earlier... > > On Wednesday 08 August 2007 03:17, Evgeniy Polyakov wrote: > > ...All oerations are not atomic, since we

Re: [1/1] Block device throttling [Re: Distributed storage.]

On Mon, Aug 27, 2007 at 02:57:37PM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: Say Evgeniy, something I was curious about but forgot to ask you earlier... On Wednesday 08 August 2007 03:17, Evgeniy Polyakov wrote: ...All oerations are not atomic, since we do not care about precise

Re: RFC: issues concerning the next NAPI interface

it is what is supposed to be dropped noticebly). -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org

Re: Distributed storage.

On Fri, Aug 03, 2007 at 09:04:51AM +0400, Manu Abraham ([EMAIL PROTECTED]) wrote: On 7/31/07, Evgeniy Polyakov [EMAIL PROTECTED] wrote: TODO list currently includes following main items: * redundancy algorithm (drop me a request of your own, but it is highly unlikley

Re: [1/1] Block device throttling [Re: Distributed storage.]

atomic_sub/dec, it can safely host additional operation). -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http

Re: [ofa-general] Re: [PATCH RFC] RDMA/CMA: Allocate PS_TCPportsfrom the host TCP port space.

e used by new RDMA connections? RDMA is not a problem, but how it influence to the network stack is. Let's better think about how to work correctly with network stack (since we already have that cr^Wdifferent hardware) instead of saying that others do bad work and do not allow shiny new feature to exist.

Re: [ofa-general] Re: [PATCH RFC] RDMA/CMA: Allocate PS_TCPportsfrom the host TCP port space.

is not a problem, but how it influence to the network stack is. Let's better think about how to work correctly with network stack (since we already have that cr^Wdifferent hardware) instead of saying that others do bad work and do not allow shiny new feature to exist. -- Evgeniy Polyakov

[1/1] w1: fix w1_remove_master_device() searching.

In case bus master driver provided bogus value as its private data, search can be incorrect. Problem found by Adrian Bunk. Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]> diff --git a/drivers/w1/w1_int.c b/drivers/w1/w1_int.c index 2fbd8dd..6840dfe 100644 --- a/drivers/w1/w1_int.c

[1/1] w1: fix w1_remove_master_device() searching.

In case bus master driver provided bogus value as its private data, search can be incorrect. Problem found by Adrian Bunk. Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED] diff --git a/drivers/w1/w1_int.c b/drivers/w1/w1_int.c index 2fbd8dd..6840dfe 100644 --- a/drivers/w1/w1_int.c +++ b

Re: [2.6 patch] w1_remove_master_device(): fix check-after-use

anoidal solution is to setup new pointer and make it equal to the found device and check if it is NULL or not out of the loop. I will cook up a patch tomorrow, thanks for pointing to this issue. -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel"

Re: Distributed storage. Mirroring to any number of devices.

with completely transparent failover recovery, with ability to detouch remote nodes from mirror array to became standalone realtime backups (or snapshots) and turn it back into the storage without stopping main device node. -- Evgeniy Polyakov - To unsubscribe from this list: send the line &q

Re: Block device throttling [Re: Distributed storage.]

On Tue, Aug 14, 2007 at 05:32:29AM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: > On Tuesday 14 August 2007 04:50, Evgeniy Polyakov wrote: > > On Tue, Aug 14, 2007 at 04:35:43AM -0700, Daniel Phillips > ([EMAIL PROTECTED]) wrote: > > > On Tuesday 14 August 2007 04:30, E

Re: Block device throttling [Re: Distributed storage.]

On Tue, Aug 14, 2007 at 04:35:43AM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: > On Tuesday 14 August 2007 04:30, Evgeniy Polyakov wrote: > > > And it will not solve the deadlock problem in general. (Maybe it > > > works for your virtual device, but I wonde

Re: Block device throttling [Re: Distributed storage.]

On Tue, Aug 14, 2007 at 04:13:10AM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: > On Tuesday 14 August 2007 01:46, Evgeniy Polyakov wrote: > > On Mon, Aug 13, 2007 at 06:04:06AM -0700, Daniel Phillips > ([EMAIL PROTECTED]) wrote: > > > Perhaps you never worrie

Re: Block device throttling [Re: Distributed storage.]

ce essentially has _no_ limit. And that as done on purpose. -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read th

Re: Block device throttling [Re: Distributed storage.]

limit. And that as done on purpose. -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: Block device throttling [Re: Distributed storage.]

On Tue, Aug 14, 2007 at 04:13:10AM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: On Tuesday 14 August 2007 01:46, Evgeniy Polyakov wrote: On Mon, Aug 13, 2007 at 06:04:06AM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: Perhaps you never worried about the resources that the device

Re: Block device throttling [Re: Distributed storage.]

On Tue, Aug 14, 2007 at 04:35:43AM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: On Tuesday 14 August 2007 04:30, Evgeniy Polyakov wrote: And it will not solve the deadlock problem in general. (Maybe it works for your virtual device, but I wonder...) If the virtual device

Re: Block device throttling [Re: Distributed storage.]

On Tue, Aug 14, 2007 at 05:32:29AM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: On Tuesday 14 August 2007 04:50, Evgeniy Polyakov wrote: On Tue, Aug 14, 2007 at 04:35:43AM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: On Tuesday 14 August 2007 04:30, Evgeniy Polyakov wrote

Re: Distributed storage. Mirroring to any number of devices.

, with ability to detouch remote nodes from mirror array to became standalone realtime backups (or snapshots) and turn it back into the storage without stopping main device node. -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message

Re: [2.6 patch] w1_remove_master_device(): fix check-after-use

new pointer and make it equal to the found device and check if it is NULL or not out of the loop. I will cook up a patch tomorrow, thanks for pointing to this issue. -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL

Re: Block device throttling [Re: Distributed storage.]

per-device limit, so that the rest of the RAM allowed to allocate all needed data structures in the network path. Above example just has 1gb of ram, which should be enough for skbs, if it is not, decrease limit to 500 mb and so on, until weighted load of the system allows to always have a forward progres

Re: Block device throttling [Re: Distributed storage.]

adjusting in-flight limit and knowing number of device it is completely possible to eliminate vm deadlock. If you do not like such calculation, solution is trivial: we can sleep _after_ ->make_request_fn() in generic_make_request() until number of in-flight bios is reduced by bio_endio().

Re: Block device throttling [Re: Distributed storage.]

On Mon, Aug 13, 2007 at 04:04:26AM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: > On Monday 13 August 2007 01:14, Evgeniy Polyakov wrote: > > > Oops, and there is also: > > > > > > 3) The bio throttle, which is supposed to prevent deadlock, can > > >

Re: Distributed storage.

y it is too big and some parts can be removed or combined, and then that size does not matter. Last/not-last checks in the code is not clear design, so I do not see why it is needed at all if not for size shrinking. > I suppose that leaving out the word "bloated" and skipping str

Re: Distributed storage.

? All this cleanups and logic complicatins should be performed only if after size shring increased number of bios can fit into cache's page, will it be done after such cleanups? -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body o

Re: Block device throttling [Re: Distributed storage.]

On Sun, Aug 12, 2007 at 10:36:23PM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: > (previous incomplete message sent accidentally) > > On Wednesday 08 August 2007 02:54, Evgeniy Polyakov wrote: > > On Tue, Aug 07, 2007 at 10:55:38PM +0200, Jens Axboe wrote: > > >

Re: [1/1] Block device throttling [Re: Distributed storage.]

virtual device will not accept any new blocks for that physical device, but can accept for another ones. That was created specially to allow fair use for network and physical storages. -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the bo

Re: Block device throttling [Re: Distributed storage.]

submits a bio recursively to our block device > * this bio blocks on the throttle > * net may never get the memory it needs, and we are wedged If system is in such condition, it is already broken - throttle limit must be lowered (next time) not to allow such situation. -- Evgeniy Poly

Re: Distributed storage.

be performed only if after size shring increased number of bios can fit into cache's page, will it be done after such cleanups? -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http

Re: Block device throttling [Re: Distributed storage.]

On Sun, Aug 12, 2007 at 10:36:23PM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: (previous incomplete message sent accidentally) On Wednesday 08 August 2007 02:54, Evgeniy Polyakov wrote: On Tue, Aug 07, 2007 at 10:55:38PM +0200, Jens Axboe wrote: So, what did we decide? To bloat

Re: Block device throttling [Re: Distributed storage.]

on the throttle * net may never get the memory it needs, and we are wedged If system is in such condition, it is already broken - throttle limit must be lowered (next time) not to allow such situation. -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux

Re: [1/1] Block device throttling [Re: Distributed storage.]

any new blocks for that physical device, but can accept for another ones. That was created specially to allow fair use for network and physical storages. -- Evgeniy Polyakov - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED

Re: Distributed storage.

design, so I do not see why it is needed at all if not for size shrinking. I suppose that leaving out the word bloated and skipping straight to the doesn't matter proof would have saved some bandwidth. :) Likely it will. -- Evgeniy Polyakov - To unsubscribe from this list: send the line

Re: Block device throttling [Re: Distributed storage.]

On Mon, Aug 13, 2007 at 04:04:26AM -0700, Daniel Phillips ([EMAIL PROTECTED]) wrote: On Monday 13 August 2007 01:14, Evgeniy Polyakov wrote: Oops, and there is also: 3) The bio throttle, which is supposed to prevent deadlock, can itself deadlock. Let me see if I can remember how

<    1   2   3   4   5   6   7   8   9   10   >