different thread in netty

Expected behavior

oh，at first i am not in English i just want to know why thread not in event loop ,the WriteBufferWaterMark not use! en, yes, in chinese 我就想知道为什么在我自己的线程中，不是netty的线程中，可以绕过WriteBufferWaterMark发送超过指定长度的消息，出于什么原因这样设计

Actual behavior

Steps to reproduce

Minimal yet complete reproducer code (or URL to code)

`private void write(Object msg, boolean flush, ChannelPromise promise) { AbstractChannelHandlerContext next = findContextOutbound(); final Object m = pipeline.touch(msg, next); EventExecutor executor = next.executor(); if (executor.inEventLoop()) { if (flush) { next.invokeWriteAndFlush(m, promise); } else { next.invokeWrite(m, promise); } } else {

            AbstractWriteTask task;
            if (flush) {
                task = WriteAndFlushTask.newInstance(next, m, promise);
            }  else {
                task = WriteTask.newInstance(next, m, promise);
            }
            safeExecute(executor, task, promise, m);
~~~~~~~~~~~~~~~~~this~~~~~~~~~~~~~~~~
        }
    }`

### Netty version
4.1.16.Final
### JVM version (e.g. `java -version`)
8u172
### OS version (e.g. `uname -a`)
linux windows

[normanmaurer]

@monkey1993 I still not understand what your issue is. Can you maybe just provide a failing unit test ?

[liewmanchoi]

@teddie-lee 其实我比较好奇的是，如果检测到了，但是netty依然将它发送到了客户端，不是应该程序手动处理吗？就像他们给的实例代码。

Could you please use English in INTERNATIONAL COMMUNITY?