netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: herbert@gondor.apana.org.au, netdev@oss.sgi.com, davem@davemloft.net
Subject: Re: Fw: 2.6.12-rc4-mm[12] - ULOG problem
Date: Thu, 19 May 2005 11:27:19 +0400	[thread overview]
Message-ID: <1116487639.21310.88.camel@uganda> (raw)
In-Reply-To: <20050519000809.2fca25c5.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]

On Thu, 2005-05-19 at 00:08 -0700, Andrew Morton wrote:
> Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
> >
> >  > Is there any reason for being able to do that?
> > 
> >  It was created to be able to load several different connector devices 
> >  from different modules [basically it was module1.ko unit=10, module2.ko
> >  unit=11 and so on].
> 
> Loading multiple instances of the same module so that we get multiple
> instances of its data structures?   That's fairly ghastly.

It was not the same module.
it was quite different module which implemented similar functionality
and used different connector device for different purposes.

> We should remove the feature.  If there is demonstrated need for multiple
> instances then it should be done by more conventional means - syscall,
> allocation of a device major then use the minor as a selector or whatever.

It is easy to use feature which prevents problems
with situation when the same socket number is used, for example, 
in 2.6 kernel while connector uses it in -mm tree.

-- 
        Evgeniy Polyakov

Crash is better than data corruption -- Arthur Grabowski

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-05-19  7:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  3:24 Fw: 2.6.12-rc4-mm[12] - ULOG problem Andrew Morton
2005-05-19  4:49 ` Herbert Xu
2005-05-19  5:27   ` Andrew Morton
2005-05-19  6:31     ` Evgeniy Polyakov
2005-05-19  6:45       ` Andrew Morton
2005-05-19  7:06         ` Evgeniy Polyakov
2005-05-19  7:08           ` Andrew Morton
2005-05-19  7:27             ` Evgeniy Polyakov [this message]
2005-05-19 13:19             ` James Morris
2005-05-19 16:53               ` Andrew Morton
2005-05-19 17:09                 ` James Morris
2005-05-19 18:54                   ` David S. Miller
2005-05-19 18:48               ` David S. Miller
2005-05-20  6:27                 ` Evgeniy Polyakov
2005-05-19 18:42           ` David S. Miller
2005-05-20  6:27             ` Evgeniy Polyakov
2005-05-19 18:44         ` David S. Miller
2005-05-20  6:39           ` Evgeniy Polyakov
2005-05-20 11:42             ` jamal
2005-05-20 14:15               ` Evgeniy Polyakov
2005-05-19 13:16     ` Fw: " James Morris
2005-05-19 13:46       ` jamal
2005-05-19 18:49         ` David S. Miller
2005-05-20  6:25           ` Evgeniy Polyakov

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=1116487639.21310.88.camel@uganda \
    --to=johnpol@2ka.mipt.ru \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@oss.sgi.com \
    /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).